<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Yes, you are correct that the resource naming scheme prevents nested<br>
resource libraries. Nested resource 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>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 nested 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>-Dan </div></div>
<br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<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://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>