> 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
>
On 2/6/06, Gary VanMatre <[EMAIL PROTECTED]> wrote:
>
> >On 2/6/06, Ryan Wynn <[EMAIL PROTECTED]> wrote:
> >>
> >> It seems the binding attribute is not getting set until the restore
> >> view phase. For example if I have
> >>
> >>
> >>
> >>
> >>...
> >>
> >> setBar is not calle
>On 2/6/06, Ryan Wynn <[EMAIL PROTECTED]> wrote:
>>
>> It seems the binding attribute is not getting set until the restore
>> view phase. For example if I have
>>
>>
>>
>>
>>...
>>
>> setBar is not called until the view is restored. I would have thought
>> that I would have acc
On 2/6/06, Ryan Wynn <[EMAIL PROTECTED]> wrote:
>
> It seems the binding attribute is not getting set until the restore
> view phase. For example if I have
>
>
>
>
>...
>
> setBar is not called until the view is restored. I would have thought
> that I would have access to the c
>It seems the binding attribute is not getting set until the restore
>view phase. For example if I have
>
>
>
>
> ...
>
>setBar is not called until the view is restored. I would have thought
>that I would have access to the component during the initial render
>phase.
>
>What I would
It seems the binding attribute is not getting set until the restore
view phase. For example if I have
...
setBar is not called until the view is restored. I would have thought
that I would have access to the component during the initial render
phase.
What I would like to do i
6 matches
Mail list logo