For the case you described, "looping through form bean properties to set or reset their values" will not work. But the solution can be improved to cover this case.
Let's keep the "looping for request parameters to set form bean properties" unchanged. In HTML tag implementation add logic to create a request to a set of property names mapping. Later, loop for all property names for the request, if the value is not presented in the request, reset the property. This way, the properties will be set no more (cover your case) and no less (cover the missing support in Struts) The de-select all options in a form when using a session scoped static form bean can be supported by Struts. Application developers are no need to struggle with different kinds of work around. --- Wendy Smoak <[EMAIL PROTECTED]> wrote: > But let's say we did it the way you describe. What > happens when I use > a single session scoped form bean across my entire > application, and > each form only uses a subset of the form bean's > properties? > > -- > Wendy __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
