On Friday, December 10, 2010 2:33 PM, Dave Newton wrote:
> if you want to do something before rendered you need to implement
PreResultListener.
I will keep this in mind.
As far as the redirect issue, I just need to rework my actions a bit, I
guess. I appreciate your wealth of knowledge, Dave.
On Fri, Dec 10, 2010 at 2:23 PM, Biesbrock, Kevin wrote:
> Ah. So is the idea that you *could* have logic in an interceptor that
> executes after the action by adding logic after invocation.invoke()?
>
Sure, like closing a Hibernate session, for example.
The caveat (to me, at least) is that the
!
Beez
r 5347
-Original Message-
From: Dave Newton [mailto:davelnew...@gmail.com]
Sent: Friday, December 10, 2010 2:15 PM
To: Struts Users Mailing List
Subject: Re: Struts Interceptors
Interceptors don't "execute in reverse order", they're each a "wrapper"
Interceptors don't "execute in reverse order", they're each a "wrapper"
around the next interceptor's execution, and eventually, the action itself.
If the interceptor is firing twice there's been to requests, which could be
a result of a redirect.
Dave
On Fri, Dec 10, 2010 at 1:50 PM, Biesbrock,
I'm not really sure how to ask this question, so please bear with me.
Requirement:
The system has several functions which a typical user can perform. The
user selects a function and the appropriate action is executed. If that
action implements myObjectAware, myObjectInterceptor retrieves myObje
5 matches
Mail list logo
