DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17751>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17751 Dynamic de-coupled mapping of DynaForm properties to Model properties Summary: Dynamic de-coupled mapping of DynaForm properties to Model properties Product: Struts Version: 0.5 Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Controller AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] BACKGROUND: =========== All my Action classes are basically doing the same thing which is: 1. authintication 2. copy the form properties to a model object 3. call the appropriate model object.method 4. handle exceptions This being a pattern, I extracted this functionality to a super Action class that is extended by all my Action classes. This super action class does the following: 1. authenticate 2. copies the form properties to a map, using BeanUtils.describe 3. reads a mapping xml and calls the appropriate model object.method using the created map, using MethodUtils.invoke 4. handle exceptions REQUIREMENT: ============ The above strategy works fine as long as the form property names and the model property names are in sync. Any change in the form property name requires a change in the model which couples the two together. If I have a way of mapping the form properties to the model properties in the <form-bean> tag may be, I can now describe the form bean into a model map and not worry about the form changes. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
