Re: [jsr-314-open] cc.parent mystery

Originally, cc meant "the current composite component" as opposed to "the composite component in this implementation section. For example, consider a login component <composite:implementation> <util:labeledInputField label="Username" value="#{cc.attrs.name}"/> <util:labeledInputField label="Password" value="#{cc.attrs.password}"/> </composite:implementation> Way back when, this wouldn't have worked IF util:labeledInputField was a composite component as well. In that case, cc would have been the labeledInputField, and it would have been necessary to use #{cc.parent.attrs.name} to get the login component's name attribute. That was fragile. It required the implementor to know which components are composite. Stuff would break if you changed the implementation of a utility component--e.g. from a regular util:labeledInputField to a composite one or the other way around. The EG then changed the definition of cc,

but apparently nobody remembered to remove the special handling of cc.parent. It is in the spec and the implementation.