/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
Try this guy:
http://struts.apache.org/2.x/struts2-core/apidocs/org/apache/struts2/ServletActionContext.html
stanlick wrote:
>
> I have an action that determines the requester IP address. The action
> implements ServletRequestAware, but I don't like it being all tangled up
> in the Servlet
why can't u get request object from ServletContext?
- Original Message -
From: "Alvaro Sanchez-Mariscal" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Monday, September 03, 2007 6:53 AM
Subject: Re: ServletRequestAware
As far as
As far as I know, the only way is asking HttpServletRequest, and thus,
implementing ServletRequestAware.
If you want to keep HttpServletRequest code out of your actions,
consider implementing an interceptor, or even a raw servlet filter.
Alvaro.
On 9/3/07, stanlick <[EMAIL PROTECTED]> wrote:
>
>
7 matches
Mail list logo
