Alias-Bean works with RI as well, but not if you use component bindings.
The problem why it doesn't work is an ommission in the spec - bindings
are restored out of the JSF-request-lifecycle, outside of a tree
iteration. I have (a long time ago) filed a bug against the spec with
regards to this - i
Hi,
i think i should recheck using aliasBean in tobago, if i remember
correct it works as a container component and the alias is valid for
all children. It should be possible in tobago having a extra container
around a component.
Regards,
Volker
2007/10/24, Mario Ivankovits <[EMAIL PROTECTE
Well, if aliasBean only works with Myfaces Core, I wonder why we even
include it with Tomahawk. It sounds like it should really be an
extension point of MyFaces Core.
In any case, it doesn't sound like a candidate for MyFaces commons at present.
On 10/24/07, Volker Weber <[EMAIL PROTECTED]> wrot
Hi Mike,
in general i'm +1 for aliasBean into the commons project, it just did
not fit into
tobago.
But there is a problem: afaik aliasBean did not work with RI.
The myfaces lifecycleImpl has a special handling of BindingAware
interface components, which are afaik only aliasBean and
aliasBeanScop
Hi!
> Why wouldn't aliasBean work as a commons project component? I
> haven't looked at the implementation, but at first glance of the docs,
> it doesn't seem to do anything renderkit-specific.
>
I think their problem is that you can use the aliasBeansScope (for
example) to group components to
Why wouldn't aliasBean work as a commons project component? I
haven't looked at the implementation, but at first glance of the docs,
it doesn't seem to do anything renderkit-specific. I looked at the
renderer implementation and it simply looks like its being used as a
callback hook back into th
