As a rule, I'd suggest creating your own base Action and extending everyting in your App from that. This gives you a place to put methods like this.
10/15/2002 2:36:44 PM, [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 18:36 ------- >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. > >Thanks, that would work; >however, then I would have to alter my actions with this rather mundane code. It's >easier to let the >tag remove it when it's finished but I understand the concern with letting view >components alter >the session. > >Perhaps the code to move the messages could be placed in a method in Action? Since >we always subclass Action this seems to be a good place and would alleviate the >burden of writing >that code each time. > >-- >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]>
