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=20996>. 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=20996 ActionForm beans plus Multiple modules can cause conflict Summary: ActionForm beans plus Multiple modules can cause conflict Product: Struts Version: 1.1 RC1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Controller AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I found a frustrating little bug in the RequestProcessor.processActionForm(). If you have 2 struts-config files foo-config.xml and bar-config.xml and each defines the following: <form-bean name="sameNameForm" type="o.a.s.v.DynaValidatorForm" > <form-property name="fooField" /> </form-bean> and <form-bean name="sameNameForm" type="o.a.s.v.DynaValidatorForm" > <form-property name="barField" /> </form-bean> respectively, then the RequestProcessor is unable to always give the correct form bean instance to the correct module. It appears this is due to the fact that storage/retrieval of these form-beans is in no way associated with the module. The workaround is to simply not use the same form-bean names in different modules. It seems the desired behavior would be to have the RequestProcessor store form- bean instances in context to the module it is configured. If I don't here contrary opinions, etc., I will work on a fix asap. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
