There was a discussion about nested resource library names last year. I would say to search the archives, but I don't know if that's possible. Anyway, here was the outcome:<br><br><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ed:<br></blockquote><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Yes, you are correct that the <span class="il">resource</span> naming scheme prevents <span class="il">nested</span><br>
<span class="il">resource</span> libraries. <span class="il">Nested</span> <span class="il">resource</span> libraries were not on the list of<br>
requirements when we designed this feature back in November of 2007. We<br>
will not accept this requirement change at this point.</blockquote></div><br>Dan:<br><br>So
the spec needs to at least be clear that it's not permitted and suggest
the alternative. Several people reading it didn't understand what to do
in this case.<br>
<br>IMHO, it's a shame that we can't use the <span class="il">nested</span>
structure. Seems like a pretty obvious convention instead of
configuration thing. I don't know how that got missed in the design
process.<br><br><br clear="all">---<br>Kito D. Mann | twitter: kito99 | Author, JSF in Action<br>Virtua, Inc. | <a href="http://www.virtua.com">http://www.virtua.com</a> | JSF/Java EE training and consulting<br><a href="http://www.JSFCentral.com">http://www.JSFCentral.com</a> - JavaServer Faces FAQ, news, and info | twitter: jsfcentral<br>
+1 203-404-4848 x3<br><br>Sign up for the JSFCentral newsletter: <a href="http://oi.vresp.com/?fid=ac048d0e17">http://oi.vresp.com/?fid=ac048d0e17</a><br><br>
<br><br><div class="gmail_quote">On Sat, Jan 30, 2010 at 6:23 PM, Cay Horstmann <span dir="ltr"><<a href="mailto:cay@horstmann.com">cay@horstmann.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have been trying to understand whether the spec allows slashes in resource library names. For example, is it within the spec to have a composite component with library name components/util?<br>
<br>
It works fine in Mojarra: Place components into resources/components/util and use a namespace alias<br>
xmlns:util="<a href="http://java.sun.com/jsf/composite/components/util" target="_blank">http://java.sun.com/jsf/composite/components/util</a><br>
<br>
But there is a catch--it won't locate a backing component in the components.util package.<br>
<br>
And per the API docs for Application#createComponent, I have no right to expect that: "Create a fully qualified Java class name by removing any file extension from resource-name and let fqcn be library-name + "." + resource-name".<br>
<br>
So, I tried to read the spec for clarification. 3.6.1.4 states: The occurrence of the string “<a href="http://java.sun.com/jsf/composite/" target="_blank">http://java.sun.com/jsf/composite/</a>” in a Facelet XML namespace declaration means that *whatever follows that last “/”* is taken to be the name of a resource library.<br>
<br>
"Whatever follows" is pretty clear. In my example, components/util would be the library name. But is it a legal library name?<br>
<br>
2.6.1.3 states "Every character in a resource identifier must be a valid character suitable for use in a string passed to the constructor<br>
of java.io.File that takes a single String argument."<br>
<br>
I don't understand this statement. In Windows, can you make files containing / symbols? If so, will slashes be treated as directory separators? What about colons? Will they be drive letters?<br>
<br>
Or are we saying it doesn't matter--we just feed the library name into the File constructor, and whatever happens, happens? Then you could have a situation where a WAR file works fine on Linux but not on Windows.<br>
<br>
Before I file an issue, could one of you tell me whether you intended to support hierarchical library names (such as components/util), or whether you envisioned only one level?<br>
<br>
Thanks,<br>
<br>
Cay<br><font color="#888888">
<br>
-- <br>
<br>
Cay S. Horstmann | <a href="http://horstmann.com" target="_blank">http://horstmann.com</a> | mailto:<a href="mailto:cay@horstmann.com" target="_blank">cay@horstmann.com</a><br>
</font></blockquote></div><br>