My first question would be how would anything (never mind Struts) address this use case?
The other half of the problem would be creating a dynamic query to go with the dynamic form, so that only the fields you are editing are updated.
-Ted.
Mete Kural wrote:
For a given form/action, the framework will be supplied with the FQCN of the DTO/VO. From there, it can determine what the fields of the form will be. The form bean validation/descriptor XML will provide the validation information and any conversion rules as needed to format/parse between the value object and the string representation for the form bean.
That sounds very interesting. I think there is interest in having support for dynamic forms where the fields of the form are determined dynamically rather than hardcoded in the JSP. What are the ideas on how to handle dynamic field names (and number of fields) in Struts 2.0?
Let's say that we are designing a dynamic customer information editing form. Every user has different preferences on what fields they want to edit or allowed to edit. Action class accesses a web service and receives a SOAP response with exactly those fields that are fit for this user. How could Struts assemble the form dynamically and pre-populate the customer information and then validate it when the user submits?
Regards, Mete
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
