Ahh, I understand. That's unfortunate. In that case, it is certainly a
limitation of ElResolver ;) and could still be enhanced.
Is this even worth considering? It would improve this particular use
case, but what else would it impact?
On Thu, 2009-03-05 at 18:33 -0800, Ryan Lubke wrote:
> On 3/5/09 6:27 PM, Lincoln Baxter, III wrote:
> > On Thu, 2009-03-05 at 11:59 -0800, Ryan Lubke wrote:
> >> No property is specified (i.e. name.<property>).
> >>
> >> From the javadocs of ELResolver.setValue():
> >>
> >> Attempts to set the value of the given property object on the given
> >> base object.
> >>
> >> So, what exactly is going to be set on the #{name} object?
> >
> > A new String object, if it has changed, unless I'm missing something
> > here.
> And set it into what? Based on ELResolver.setValue() we need both a base
> and a property. The expression #{name} provides only the base.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: webtier-help_at_glassfish.dev.java.net
>