[jsr-314-open] organizing composite component templates

[Dan Allen]

>
>
> Yes, you are correct that the resource naming scheme prevents nested
> resource libraries.  Nested resource libraries were not on the list of
> requirements when we designed this feature back in November of 2007.  We
> will not accept this requirement change at this point.


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.

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.

-Dan


-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jsr-314-open-mirror/attachments/20090413/548caab5/attachment.html