The action messages and errors are stored in a request attribute which is
why the don't survive a redirect.
I played around with some ideas and found that Freemarker (the template
language used for the tags), is just too dumb to clear session scoped
variables (which would survive a redirect and are used by the
MessageStoreInterceptor), so I guess we're kind of stuffed until someone
works on the core code and comes up with a method that works.
Al.
P.S. The errors are delt with inside Xwork and not S2.1, so it's not a
simple job :(.
----- Original Message -----
From: "Chris Pratt" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <user@struts.apache.org>
Sent: Thursday, April 03, 2008 4:42 PM
Subject: Re: [DEV-IMPLICATIONS] Re: Actionerrors & the Store Interceptor
On Thu, Apr 3, 2008 at 1:03 AM, Al Sutton <[EMAIL PROTECTED]> wrote:
Chris,
I'm familiar with the code, but the main problem is that there is a
"paper
wall" between the StoreInterceptor and the jsp tags, so that one does not
know or rely on how the other works.
As far as I'm aware this is only a philosophical decision, and there is
no
technical reason why the tags can't removed information stored in the
StoreInterceptor, but I'm pretty sure it would need the nod of those on
the
dev list to get into the final build.
Actually it wouldn't be removing information stored in the
StoreInterceptor as much as removing the already shown messages from
the lists stored in the Action. So, by the time he StoreInterceptor
got control, there would be nothing to store.
(*Chris*)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
