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=13837>. 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=13837 DynaActionForm is not sensitive to sub-application ------- Additional Comments From [EMAIL PROTECTED] 2002-10-22 16:02 ------- The bug report is valid :-(. What's going on is that the DynaActionForm infrastructure (ultimately based on BasicDynaBean and BasicDynaClass from beanutils) uses the form name (in the absence of any other information as the "fully qualified class name" for creating a BasicDynaClass. Because the cache of BasicDynaClass names is global to the entire webapp, that means using the same form name in two different struts-config.xml files is going to clash. I need to look at the proposed solution, though, to make sure it doesn't mess up applications. -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
