How about something in your Action that moved the message from the Session to Request, so that the tags would not be messing about with the system state?
-Ted. 10/15/2002 11:27:16 AM, [EMAIL PROTECTED] wrote: >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=13565>. >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=13565 > >To "errors", add prefix, suffix, header, footer attrs, to "messages", add prefix, >suffix attrs > > > > > >------- Additional Comments From [EMAIL PROTECTED] 2002-10-15 15:27 ------- >I have written a custom tag that is very similar to the messages tag but with the >scope and remove >attributes. I made this to address the following situation: > >When the user submits a form I >redirect back to the menu page. I redirect rather than forward to prevent the user >accidently >reposting form data (Craig might say that I should train my users but that's another >debate ;-). I >want to display a message on the menu page following the form submission; this >message must go in >the session because of the redirect. > >The remove attribute is needed when messages are in the >session because the tag would display the message every time if it's not removed. I >didn't follow >your suggestion on how to accomplish this but I'm certainly open to alternatives. > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
