>Sorry, I didn't do a very good job of explaining. I was trying to describe
>the recursiveness of the XML
>where symbols defined in a outer scope are passed on to nested components but
>nested components can override.
>
><component jsfid="baseInput" extends="inputText">
> <attributes>
> <set name="styleClass" value="#{shale.attributes.class}"/>
> <set name="value" value="#{shale.managed-bean-name.street1}"/>
> </attributes>
> <symbols>
> <set name="class" value="defaut"/>
> </symbols>
></component>
>
>
><component jsfid="addressPanel" extends="panelGrid">
> <attributes>
> <set name="columns" value="1"/>
> </attributes>
>
> <element renderId="0" jsfid="baseInput" id="street1"/>
> <element renderId="1" jsfid="baseInput" id="street2">
> <symbols>
> <set name="class" value="override"/>
> </symbols>
> </element>
></component>
>
>In this example, street1 should have a 'styleClass=default' and
>street2 will have a 'styleClass=override'.
>
>Unless the "class" symbol was saved multiple times in the request with a
>unique name, the last value would take precedence.
Hey Craig, what about creating ValueBinding and MethodBinding decorators and
hang the symbol table off the decorated binding object? A similar approach to
how literal string action's are handled.
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
