It can't happen, any more than a single attribute can represent both a
Float and a Date at the same time.
There's no way for java code to know if "#{x.y}" is a value binding or
a method binding dynamically. You have to pick one or the other as
the underlying data type for the attribute. Thus aliasBean and the
Facelet and Clay equivalents all pick value binding.
On 12/24/05, Dave <[EMAIL PROTECTED]> wrote:
> Thanks, Mike.
>
> It would be very nice if JSF (or MyFaces) allow method binding for backing
> bean. It would allow a different way of design and thinking: backing bean
> changes dynamically without page navigation.
>
> Mike Kienenberger <[EMAIL PROTECTED]> wrote:
> I'm pretty sure that the value has to be a value binding and not a
> method binding.
> The same issue came up on the facelets user list, and the recommended
> solution is to pass a backing bean that implements your method
> binding.
>
> Ie,
>
>
>
> and in your aliased code....
>
> action="#{backBeanImplementor.backBean}"
>
>
> On 12/23/05, Dave wrote:
> >
> >
> >
> > summaryBean.backBean is a method binding that returns a Backing bean for
> the
> > alias. I got error "backing bean is null" during restoreView/render phase.
> > It seems that JSF can not tell if it is the name of the backing bean or
> > method binding. But JSF should be able to tell the difference because
> method
> > binding has a dot(.). Is this a bug? or JSF does not support it? Thanks.
> >
> >
> >
> > .....
> >
> >
> >
> >
> > ________________________________
> > Yahoo! Photos
> > Ring in the New Year with Photo Calendars. Add photos, events, holidays,
> > whatever.
> >
> >
>
>
>
>
> ________________________________
> Yahoo! DSL Something to write home about. Just $16.99/mo. or less
>
>
