Hi @ll,
I have a JSP page that contains:
<stripes:select name="someName" value="someValue">
<stripes:options-enumeration enum="someClass" />
</stripes:select>
After spending a good while trying to figure out why stripes would not
set the selected="selected" flag even though simply adding ${someValue}
next to the select revealed that the value passed to stripes was
correct, I discovered that stripes would simply ignore the value I
supplied if it can find another value querying the population strategy.
The value I supplied is overwritten in class
net.sourceforge.stripes.tag.InputSelectTag on line 125.
Unfortunately in my case stripes found such a value on my action bean.
This leaves me with two questions:
1. Is this really intended behaviour? After all, why would I use the
value attribute if I did not mean it?
2. Is there anything I can do about the behaviour besides changing my
variable names or changing/extending stripes tag-lib?
Thomas
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
