DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=32176>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32176 remove "scope" from element "action" in struts-config_1_2.dtd Summary: remove "scope" from element "action" in struts- config_1_2.dtd Product: Struts Version: 1.2.4 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] As per Bug 31320 when migrating to 1.2.4, I set the scope to "session" as the path of least resistance to gain backward compatibility. Unfortunately, this seems to "ask for trouble" when having <html:checkbox on the form: 1) if the form is for example a user profile that a user might update many times to get familiar with the options, after checking the box, it will not be possible to uncheck it anymore. Unchecking appears only to be possible if the user does so when encountering the form for the first time (i.e. it is not yet in the session ==> pre-filling the form happens from some other bean in the session) 2) if the checkboxes are built from a list with logic:iterate and a user uses the browser back-button (before an Action.execute() had a chance to clean that form bean from the session), it may even happen that in the session there are checkbox values visible to Action.execute() that were not visible in the jsp page because the list had changed in the meantime. Therefore my suggestion is to remove the scope attribute and default its value to "request". --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
