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=10979>. 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=10979 DynaActionForm in session losts datas. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2002-07-27 18:59 ------- Fixed in nightly build 20020728. Your analysis of how RequestUtils.createActionForm() was checking for whether an existing instance can be recycled is correct -- it was incorrectly accepting *any* DynaActionForm instance stored under the same session attribute key, instead of just one for the particular form bean being requested. However, it is unlikely that anyone would have actually run into this bug, unless they were using the "attribute" attribute on an <action> to cause the form beans for different forms to be stored under the same key. The contract for form beans is that the reset() method should reset all properties to their initial state. In particular, this is required to make sure that boolean properties corresponding to checkboxes are set correctly. If you need your reset() method to have different behavior, you will need to subclass DynaActionFormBean and implement a custom reset() method. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
