[jsr-314-open] cc.parent mystery

[Andy Schwartz]

Hi Ed -

Ed Burns wrote:
> AS> Okay, this seems like an oversight to me.  I have logged the following 
> AS> issue to request that we remove this from the spec:
>
> AS> https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=741
>
> AS> Any objections to making this change in the MR?
>
> I'm not sure about removing this statement.  The section you quote is
> for the special composite component ELResolver, the thing that makes the
> #{cc.attrs} magic work.

Right. Note that we aren't proposing that we should remove the entire 
section. Just one sentence:

> > If base is non-null, is an instance of UIComponent, is a composite
> > component, and property is non-null and is equal to the string
> > “parent”, call the static method
> > UIComponent.getCompositeComponentParent() passing base as the
> > argument, returning the result.

This should have no impact on the ELResolver's ability to resolve 
#{cc.attrs}.


>   If we remove this statement, then the
> following, currently supported, code will cease to work.
>   

Which code? I don't see the use case that you are referring to.


> I have removed the corresponding code in my local workarea and am
> currently re-running the automated tests.

Okay, thanks. If we have a test that explicitly checks that #{cc.parent} 
is resolved to the nearest composite component ancestor as opposed to 
just the immediate parent, such a test case would fail after this change.

Andy