Hmm... I have not thought about the binding conflicts.
Think of it - maybe we can specify a rule that the page scope gets the binding
first, the come the bindings from the parameters.
Re the request scope - it is too short.
Persisting values in the browser is a all too common requirements. For example a
web page that view/edit a customer almost invariably has something like:
<stripes:hidden name="customerId" value="${actionBean.customerId}" />
I still think having the browser scope is a nice idea.
Cheers,
Chut
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
