> > so not:
> >
> > // Retrieve the required property value
> > Object value = this.value;
>
> This will return null if you did not specify a "value" attribute, so the
> effect is the same as your desired result -- setting the new bean based on
> the name/property combination.
This is not my desired result because i want it to be a default value.
It should not ignore the name and property attributes if they are specified.
> > // Retrieve the required property value
> > Object value = null;
> > if(name != null)
> > value = RequestUtils.lookup(pageContext, name, property, scope);
> > if (value == null)
> > value = this.value;
> >
>
> This would reverse the priority of lookups, and make the string you
> specified for the "value" essentially a default if the specified property
> returns null. That is different from the current behavior, and different
> from what is documented, but makes a certain kind of sense.
But the behaviour is not changed for all the application build today
because None in using a name, value combo because at this time
that combo doesn't make any sense because it doesn't do a thing.
> What do people think about changing this?
You got my vote!
johan
