On 7/22/09 7:37 AM, webtier_at_javadesktop.org wrote:
> Thank you for the quick response. It's hard to find such documentation and your tips are really valuable.
>
>
>> What about #{component}? This resolves to the currently processing
>> component. You can access the attributes map
>> with expressions such as #{component.attributes['attrName']}.
>>
>
> I think I tried this before but it's not working as expected if the components are nested. I tested it today and inside the nested component it gives me the parent one.
>
Can you offer a more concrete example of what you're trying?
>
>
>> <facelet-taglib>
>> <namespace>http://domain.com/path</namespace>
>> <composite-library-name>compositeTest</composite-library-name>
>> </facelet-taglib>
>>
>
> This is cool and eliminated the need to specify the tags manually in the taglib file. I started using it and quickly ported all my current facelet tags to composite components.
>
>
>> There are no plans to allow composite components to exist outside of
>> /resources or META-INF/resources
>> at this point in time. However, you can provide a custom
>> ResourceHandler implementation to find resources
>> in which ever directory you wish.
>>
>
> I understand that this is related to the ability to have such files in JARs. The custom location is not that important.
>
> Thanks again!
> [Message sent by forum member 'rostislav' (rostislav)]
>
> http://forums.java.net/jive/thread.jspa?messageID=356987
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: webtier-help_at_glassfish.dev.java.net
>
>