On 4/21/09 2:25 PM, Lincoln Baxter, III wrote:
> Excellent, thanks! This is good to hear.
I've just committed changes to support the new functionality.
1. composite:renderUsingPageChildren has been removed.
2. composite:insertFacet does just what it says now. It
moves the facet of the composite component to the
parent component in which composite:insertFacet is nested
within.
3. added composite:insertChildren. This tag moves
the children of the composite component to
the component in which composite:insertChildren is
nested within.
4. added composite:renderFacet. This should be used
when a composite component has a facet that needs
to be displayed (i.e. it's not a facet of a component
within the composite:implementation section).
>
> On Tue, 2009-04-21 at 19:04 +0200, Ed Burns wrote:
>> >>>>> On Sat, 11 Apr 2009 09:16:17 -0700, Ryan Lubke<Ryan.Lubke_at_Sun.COM <mailto:Ryan.Lubke_at_Sun.COM>> said:
>>
>> RL> This is the correct behavior. The 'renderUsingPageChildren' renders the
>> RL> output of a component in
>> RL> the location referenced by that tag. If the children being referenced
>> RL> don't have renderers (as selectItems
>> RL> do not), then no output will be produced.
>>
>> RL> Currently, and this may change in time for 2.0, there is no way to
>> RL> re-locate children of a composite
>> RL> component to a location within the composite component
>> RL> implementation.
>>
>> As Ryan said, it did change. I'll publish another Editor's Draft of the
>> spec to our public area and announce it on my blog.
>>
>> Ed
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:webtier-unsubscribe_at_glassfish.dev.java.net <mailto:webtier-unsubscribe_at_glassfish.dev.java.net>
>> For additional commands, e-mail:webtier-help_at_glassfish.dev.java.net <mailto:webtier-help_at_glassfish.dev.java.net>
>>
>>