On 9/26/05, Sylvain Vieujot <[EMAIL PROTECTED]> wrote:
If you were going to include both tomahawk and sandbox in a single JAR file, why not just include both TLDs in the META-INF directory of that JAR file? There's no limit on how many TLDs you can have ... but, more importantly, that would mean a developer would not have to recode all their JSP pages when they switched from separate jars to the combined jar, or back again.
Craig
PS: You'll still need to do an automated merge the faces-config.xml files that define the two sets of components, into a single /META-INF/faces-config.xml file in the combined JAR, but that's invisible to the developer. Merging tag libraries is *not* invisible, and is therefore something I would discourage.
You're right, this is how it is right now :
<uri>http://myfaces.apache.org/tomahawk</uri>, with recommended prefix t: for Tomahawk
<uri>http://myfaces.apache.org/sandbox</uri>, with recommended prefix s: for Sandbox
<uri>http://myfaces.apache.org/all</uri>, with recommended prefix x: for All components (Tomahawk + Sandbox)
If you were going to include both tomahawk and sandbox in a single JAR file, why not just include both TLDs in the META-INF directory of that JAR file? There's no limit on how many TLDs you can have ... but, more importantly, that would mean a developer would not have to recode all their JSP pages when they switched from separate jars to the combined jar, or back again.
Craig
PS: You'll still need to do an automated merge the faces-config.xml files that define the two sets of components, into a single /META-INF/faces-config.xml file in the combined JAR, but that's invisible to the developer. Merging tag libraries is *not* invisible, and is therefore something I would discourage.
