/nod
On Tue, Jan 13, 2009 at 4:14 PM, Dave Newton wrote:
> Andy wrote:
>>
>> Your first point makes total sense. [...]
>> The second point also makes sense. [...]
>
> That's like the most sense I've ever made in one day ever.
>
> Makes me wonder if it was really me that sent the message.
>
> Dave
Andy wrote:
Your first point makes total sense. [...]
The second point also makes sense. [...]
That's like the most sense I've ever made in one day ever.
Makes me wonder if it was really me that sent the message.
Dave
-
To
uts.apache.org
> Subject: Re: ServletRequestAware interface
>
> Andy wrote:
> > Having my s2 action classes implement ServletRequestAware works great
> > for getting request parameters.
>
> It's not necessary, though, as S2 will set request parameters into
> acti
Andy wrote:
Having my s2 action classes implement ServletRequestAware works great
> for getting request parameters.
It's not necessary, though, as S2 will set request parameters into
action properties (a) without the overhead of getting the request
parameters manually, and (b) without tying y
Having my s2 action classes implement ServletRequestAware works great for
getting request parameters. However it doesn't look like non-action classes
can implement this interface to get the parameters. Since I offload my action
class execute() processing to a service class (which is injected
mojoRising wrote:
I am using the Execute and Wait Interceptor on my login action. This action
needs to access the HTTPRequest object so that it can get the HTTPSessionId,
and the request headers and store all of this in the database as well as
putting the userObject in the session itself.
Docume
(not the SessionMap).
I am in a quandry. Do I need to implement both interfaces? Is
ServletRequestAware as reliable when using execAndWait as SessionAware is?
--
View this message in context:
http://www.nabble.com/Does-Execute-and-Wait-Interceptor-work-with-ServletRequestAware-interface
7 matches
Mail list logo
