+1
Although, I like the <component> wrapper vs. <composite-component>.
-Ken
On 06/10/2011 10:54 AM, Andy Schwartz wrote:
> Ed -
>
> On 5/13/11 11:37 AM, Ed Burns wrote:
>> Allow cc and non-cc components in one taglib
>> http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1001
>>
>
>
> This is a great addition to the spec! Thanks for getting this in.
>
> I have one small suggestion, regarding the proposed taglib.xml syntax:
>
>
>> <tag>
>> <tag-name>layout</tag-name>
>> <resource-id>myCC/whatever.xhtml</resource-id>
>> </tag>
>
>
> The <tag> construct is a very generic thing in Facelets - ie. it is
> used not just to define components, but validators, converters, and
> source fragments as well. Since "resource" is also a very generic
> concept, it would be clearer if we explicitly specified that we are
> declaring a component tag.
>
> We could use the existing <component> element for this purpose, eg:
>
>
> <tag>
> <tag-name>layout</tag-name>
> <component>
> <resource-id>myCC/whatever.xhtml</resource-id>
> </component>
> </tag>
>
>
> Or make this even more explicit by introducing a new
> composite-specific wrapper element, eg:
>
>
> <tag>
> <tag-name>layout</tag-name>
> <composite-component>
> <resource-id>myCC/whatever.xhtml</resource-id>
> </composite-component>
> </tag>
>
>
> This makes the intention clearer and also leaves open the possibility
> that we may define other types of (non-component) resource-based tags
> in the future.
>
> Thoughts?
>
> Andy
>