tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Stang" <mst...@pingidentity.com>
Subject T5: Brandable
Date Mon, 29 Jan 2007 23:30:41 GMT
We ship two versions of our product.  The first is a Ping Identity version, says Ping Identity/PingFederate
all over it.  The other version is "branded" for our OEM customer to re-sell.  In T3, in order
to do this I have two jar files to implement this.  Each is a Tapestry Library.  

When I have a "branded" component I do something like this:

   <span jwcid="@branded:HeaderLogo"/>

However, I have had to create hacks to work-around issues like the .application file.  I have
a Library refence:

<library id="branded" specification-path="/com/pingidentity/component/branded/Branded.library"/>

And then I generate a "Branded.library" for each release and copy to the above location.

1 <!DOCTYPE library-specification PUBLIC "-//Apache Software Foundation//Tapestry Specification
3.0//EN" "http://jakarta.apache.org/tapestry/dtd/Tapestry_3_0.dtd"><library-specification>
 2   <library id="common" specification-path="/com/pingidentity/component/common/PingCommon.library"/>
 3   <component-type type="About" specification-path="ping/About.jwc"/>
 4   <component-type type="Licensing" specification-path="ping/Licensing.jwc"/>
 5   <component-type type="HeaderLogo" specification-path="ping/HeaderLogo.jwc"/>
 6   <component-type type="LoginHeader" specification-path="ping/LoginHeader.jwc"/>
 7   <component-type type="Support" specification-path="ping/Support.jwc"/>
 8   <component-type type="Welcome" specification-path="ping/Welcome.jwc"/>
 9   <component-type type="AdditionalResources" specification-path="ping/AdditionalResources.jwc"/>
10   <component-type type="PingLogo" specification-path="ping/PingLogo.jwc"/>
11   <component-type type="ConnectionLimit" specification-path="ping/ConnectionLimit.jwc"/>
12   <component-type type="AdditionalAdapters" specification-path="ping/AdditionalAdapters.jwc"/>
13 </library-specification>

What I would like in T5 is some support for being able to "brand" components.



Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message