From: Ed Burns <Ed.Burns_at_Sun.COM>
Date: Thu, 23 Apr 2009 11:13:26 +0200

>>>>> On Wed, 22 Apr 2009 10:44:53 -0700, Ryan Lubke <Ryan.Lubke_at_Sun.COM> said:

RL> On 4/21/09 2:25 PM, Lincoln Baxter, III wrote:
>> Excellent, thanks! This is good to hear.
RL> I've just committed changes to support the new functionality.

RL> 1. composite:renderUsingPageChildren has been removed.
RL> 2. composite:insertFacet does just what it says now. It
RL> moves the facet of the composite component to the
RL> parent component in which composite:insertFacet is nested
RL> within.
RL> 3. added composite:insertChildren. This tag moves
RL> the children of the composite component to
RL> the component in which composite:insertChildren is
RL> nested within.
RL> 4. added composite:renderFacet. This should be used
RL> when a composite component has a facet that needs
RL> to be displayed (i.e. it's not a facet of a component
RL> within the composite:implementation section).

Ryan, I've added this attribute to <comp:renderFacet>.

        <attribute>
            <description>
                <![CDATA[
<div class="changed_added_2_0">

<p>If <code>true</code>, and there is no such facet present on the top
level component, a <code>TagException</code> must be thrown, containing
the <code>Location</code>, the facet name, and a localized descriptive
error message.</p>

</div>]]>
                
            </description>
            <name>required</name>
            <required>false</required>
            <deferred-value>
                <type>boolean</type>
            </deferred-value>
        </attribute>

You mentioned on Skype that it would be useful and I agree. Can you
please ensure it gets added to the implementation?

Thanks,

Ed