On 9/1/06, Wang, Sherwin X. <[EMAIL PROTECTED]> wrote:
Could this approach resolve this problem so that make Struts more powerful? Instead of "looping through parameters in a request" and setting the form bean properties, could the logic "loop through the form bean properties" and set them by retrieving the values from the request? For a certain property, if the value doesn't present in the request, reset this property.
I thik the behavior you are describing can be achieved by changing your form bean to request scope. They you start with an empty form bean every time, and only the values present in the request will be populated. 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
