> I agree. I took a peek at the myfaces UIComponentTag and in the
> "createComponentInstance" method there is a check for the existence of
> a "binding" attribute. If there is one, the component instance pulled from
> the target managed bean. Otherwise, it's using the createComponent factory
> method on the application.
>
> The Clay component is not respecting the "binding" attribute when creating
> the component subtree. It should use the binding attribute to create the
> component
> and ignore it when setting the property values of the component.
>
> Does this sound correct?
I think this is correct, Gary. But just to clarify I would say
if creating comp and
binding attribute set and
evaluation of binding in target managed-bean == null
then create the component using the createComponent factory and
set the instance into the target bean.
otherwise, managed-bean has already created it so just use it.
My understanding was that the target bean need not create the
component instance, but that the instance would always be bound to the
target bean. I thought it was an IoC thing.
in all cases you would want to disregard binding when setting the
property values.
