Thank Cay.<br><br>Let's get it done.<br><br>-Dan<br><br><div class="gmail_quote">On Thu, Feb 4, 2010 at 6:10 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;">It's at <a href="https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=740" target="_blank">https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=740</a>. What a mess!<br>
<br>
At least it paves the way towards handling hierarchical library names in the future, should you choose to do so.<div class="im"><br>
<br>
On 02/03/2010 09:12 AM, Dan Allen wrote:<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
Cay, could you organize your comments into a spec issue?<br>
<br>
Thx,<br>
<br>
-Dan<br>
<br>
On Wed, Feb 3, 2010 at 11:18 AM, David Geary <<a href="mailto:clarity.training@gmail.com" target="_blank">clarity.training@gmail.com</a><br></div><div class="im">
<mailto:<a href="mailto:clarity.training@gmail.com" target="_blank">clarity.training@gmail.com</a>>> wrote:<br>
<br>
+1. This should definitely be fixed.<br>
<br>
<br>
david<br>
<br>
2010/2/3 Dan Allen <<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.com</a><br></div>
<mailto:<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.com</a>>><div class="im"><br>
<br>
On Mon, Feb 1, 2010 at 11:07 AM, Jason Lee<br></div><div><div></div><div class="h5">
<<a href="mailto:jason@steeplesoft.com" target="_blank">jason@steeplesoft.com</a> <mailto:<a href="mailto:jason@steeplesoft.com" target="_blank">jason@steeplesoft.com</a>>> wrote:<br>
<br>
On 2/1/10 9:13 AM, Kito Mann wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There was a discussion about nested resource library names<br>
last year. I would say to search the archives, but I don't<br>
know if that's possible. Anyway, here was the outcome:<br>
<br>
Ed:<br>
<br>
Yes, you are correct that the resource naming scheme<br>
prevents nested<br>
resource libraries. Nested resource libraries were not<br>
on the list of<br>
requirements when we designed this feature back in<br>
November of 2007. We<br>
will not accept this requirement change at this point.<br>
<br>
<br>
Dan:<br>
<br>
So the spec needs to at least be clear that it's not<br>
permitted and suggest the alternative. Several people<br>
reading it didn't understand what to do in this case.<br>
<br>
IMHO, it's a shame that we can't use the nested structure.<br>
Seems like a pretty obvious convention instead of<br>
configuration thing. I don't know how that got missed in<br>
the design process.<br>
</blockquote>
It would be interesting to find out why that was left out.<br>
Was it simply an oversight, or are there technical reasons<br>
for disallowing that? On the surface, it sounds like it<br>
would be easy to implement and support, but I've not thought<br>
too deeply on the topic. Maybe that's something we should<br>
fix, if we can, for 2.1.<br>
<br>
<br>
We never got to the bottom of why this was left out, but I think<br>
there was a general agreement that it should be fixed. Let's<br>
discuss when and get an issue report filed.<br>
<br>
Here is the (not-so-pretty) link to the original discussion:<br>
<br>
<a href="http://archives.java.sun.com/cgi-bin/wa?A1=ind0904&L=JSR-314-OPEN&X=3E023C7A0F922F9C1F#16" target="_blank">http://archives.java.sun.com/cgi-bin/wa?A1=ind0904&L=JSR-314-OPEN&X=3E023C7A0F922F9C1F#16</a><br>
<<a href="http://archives.java.sun.com/cgi-bin/wa?A1=ind0904&L=JSR-314-OPEN&X=3E023C7A0F922F9C1F#16" target="_blank">http://archives.java.sun.com/cgi-bin/wa?A1=ind0904&L=JSR-314-OPEN&X=3E023C7A0F922F9C1F#16</a>><br>
<br>
(that reminds me I have some leaning on the JCP PMO to get to).<br>
<br>
-Dan<br>
<br>
--<br>
Dan Allen<br>
Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br>
<br></div></div>
<a href="http://mojavelinuxcom" target="_blank">http://mojavelinuxcom</a> <<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a>><div class="im"><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.jallen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
<br>
<br>
<br>
<br>
<br>
--<br>
Dan Allen<br>
Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br>
<br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
</div></blockquote>
<br><div><div></div><div class="h5">
<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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>