Mailing List user@struts.apache.org
Sent: Wednesday, April 02, 2008 10:55 PM
Subject: Re: Actionerrors the Store Interceptor
Sorry Lucas, I'm still not seeing how that will help differentiate
between which result's need the messages collected and which don't?
And I have to agree with Laurie
On Wed, Apr 2, 2008 at 11:17 PM, Al Sutton [EMAIL PROTECTED] wrote:
Chris,
I've used the StoreInterceptor and my opinion is that it just isn't
flexible enough to use.
To illustrate the point, consider try following;
1) You have a View Action which displays all of the data of a specific
: Thursday, April 03, 2008 7:31 AM
Subject: Re: Actionerrors the Store Interceptor
On Wed, Apr 2, 2008 at 11:17 PM, Al Sutton [EMAIL PROTECTED] wrote:
Chris,
I've used the StoreInterceptor and my opinion is that it just isn't
flexible enough to use.
To illustrate the point, consider try following
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
[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
We're having a problem configuring the system and, since this seems
like a common problem, we're hoping someone has found a solution.
We have a bunch of actions that can't be run twice, so we're using the
redirect-action result type to make sure a refresh doesn't
accidentally resubmit the
Hi,
I think the best solution is to develop two Interceptors, one will run
after action invocation and will store messages in session or some
other objects from given request key. And second one, which will be
run before action invocation, that will retrieve such stored messages
from session and
Lukasz Lenart wrote:
Hi,
I think the best solution is to develop two Interceptors, one will run
after action invocation and will store messages in session or some
other objects from given request key. And second one, which will be
run before action invocation, that will retrieve such stored
Thanks Laurie, any ideas on the original problem?
(*Chris*)
On Wed, Apr 2, 2008 at 2:19 PM, Laurie Harper [EMAIL PROTECTED] wrote:
Lukasz Lenart wrote:
Hi,
I think the best solution is to develop two Interceptors, one will run
after action invocation and will store messages in session
Umm, that's what the Store Interceptor is.
Not exactly, you have to specify for which action store the messages,
and for which retrieve them back. There is no magic, everything hand
coded ;-)
Regards
--
Lukasz
http://www.linkedin.com/in/lukaszlenart
Sorry Lucas, I'm still not seeing how that will help differentiate
between which result's need the messages collected and which don't?
And I have to agree with Laurie, that I don't understand the
difference between the store interceptor and what you're proposing.
(*Chris*)
On Wed, Apr 2, 2008
11 matches
Mail list logo
