Re: [jsr-314-open-mirror] [jsr-314-open] composite:attribute "targets" property does not match with ViewDeclarationLanguage.retargetMethodExpressions

[...] LU> There are two possible alternatives here: LU> 1. Implement the algorithm proposed for retargetMethodExpressions LU> and ignore composite:attribute "targets" property says. LU> 2. Implement the expected behavior of composite:attribute "targets" LU> property and make some changes to retargetMethodExpressions LU> algorithm. LU> The intention is take option 2 and include it for JSF 2.0, because LU> in theory should be handled as an implementation detail of the LU> algorithm (anyway it could be good to update the documentation with LU> the same advice used for retargetAttachedObjects). Certainly you have identified a valid issue. The root problem is that the top level component needs to have a Java programming way to expose its composite-ness. LU> For "action", "actionListener", "validator" and LU> "valueChangeListener" it is clear that the action to take is LU> something like this: LU> - If target is a composite component and that one "retarget" to LU> other components and additionally does not implements LU> [ActionSource2/EditableValueHolder], call: LU> targetComponent.getAttributes().put(attributeName, LU> attributeNameValueExpression); LU> and call retargetMethodExpressions recursively. Take care of LU> apply the method twice and if the property pointed by LU> "attributeName" was already set, revert its effects. The solution you propose will work, but it feels a bit too implementation-ish. Right now we declare that every compositeComponent must be a NamingContainer. Perhaps it's time to define a new abstract sub-class of NamingContainer that is a union of all the behavioral interfaces? public abstract class javax.faces.component.CompositeComponent implements NamingContainer, ActionSource2, EditableValueHolder { public abstract void acceptRetargetedMethodExpressions(BeanInfo ccMetadata); } LU> The tricky part is how to handle generic method expression LU> properties. The javadoc says: We could specify whatever we needed in that acceptRetargetedMethodExpressions() method. Ed -- | edward.burns(a)oracle.com | office: +1 407 458 0017 | homepage: | http://ridingthecrest.com/ | 16 work days until German Oracle User's Group Conference