[ http://issues.apache.org/struts/browse/STR-2494?page=comments#action_38083 ] Michael Jouravlev commented on STR-2494: ----------------------------------------
If Conversation Scope is implemented (http://issues.apache.org/struts/browse/STR-2939), then messages queued to session scope should be retained there. This would be the logical change. Yes, it will break the compatibility with older versions, but I think that it will be a proper thing to do. Stuff stored in the session should not expire automagically, new Conversation Scope will be used for that. > Make an option to NOT automatically remove messages from session after > redirect > ------------------------------------------------------------------------------- > > Key: STR-2494 > URL: http://issues.apache.org/struts/browse/STR-2494 > Project: Struts 1 > Issue Type: Improvement > Components: Core > Affects Versions: 1.2.7 > Environment: Operating System: other > Platform: Other > Reporter: Michael Jouravlev > Assigned To: Struts Developers > Priority: Minor > > Currently (from 1.2.6?) RequestProcessor removes messags automatically once > they > were accessed. For the dialog functinality it is necessary that a user should > be > able to reload a page any number of times, and still be able to see its > content > with error messages intact. > I would prefer RequestProcessor to either stop removing messages from session, > or to have a parameter for not removing them. Seems that currently I have to > override processCachedMessages to remove this functionality. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
