Comments on: Struts 2 Tutorial – Interceptors

By: Gagan

Gagan — Fri, 15 Jul 2011 12:38:32 +0000

How can I redirect user request coming from mobile or desktop users to different views. Can I use the interceptor or is there any easy way.

By: makku

makku — Wed, 22 Jun 2011 11:39:10 +0000

nice example

By: emmanuel

emmanuel — Sun, 12 Jun 2011 06:53:32 +0000

i need struts2 configuration and how interceptors work with struts can any one help me?

By: Leo

Leo — Fri, 20 May 2011 17:41:41 +0000

Thank you for the post and examples. It did solved my problem.
I was having problem handle logic between action and result until I know about the PreResultListener.
Such a great help!

By: Rafance

Rafance — Mon, 14 Feb 2011 21:26:18 +0000

Hi, I need help with a situation with my struts2 project.
I try to read a numerical value using the following code:

the parameter numeroCedula it will be passed to the my action…
but, I write into the textbox by example “9978222″ and when i submitted the value, I receive in the action the value “9978222,” , why the struts2, I don’t know if some interceptors change the value, adding this coma after the numerical value.

Could somebody help me?

thanks you

By: upendra

upendra — Wed, 19 Jan 2011 11:49:34 +0000

This is really a nice peace of code regarding interceptor……..its very helping…..
I want to know …can this example is useful incase of that case when we use strut2 and hibernate at the same time….plz repply on my emailid….
thanks in advance…

By: Nishigandha

Nishigandha — Tue, 11 Jan 2011 20:09:49 +0000

Fantastic example. Very much simplified difficult topic.

By: praveen

praveen — Wed, 25 Aug 2010 03:57:25 +0000

good example .

By: billy vandory

billy vandory — Thu, 17 Jun 2010 08:41:04 +0000

@Arnie: OSIV is a valid pattern. Arnie, it may have caused you grief, but to advise everyone NOT TO USE IT is a little cocky, no? There are use cases when OSIV may work just fine, like a backoffice application where the need to break out the layers into tiers with some kind of facade separating concerns is not doable due to project timelines and costs.

By: Ben

Ben — Sat, 06 Feb 2010 17:31:39 +0000

Kamlesh, what you are talking about is tying a login to an IP address. You can invalidate the session ID if the IP address changes or ignore all new session requests while there is an active session under an old IP address. This can present usability problems to some users if their IP address changes. Another option would be to present an alert to the user that the IP address logged in has changed. For example, GMail lists the last account activity on the page. You should log these instances as well in case they present a security incident. You’ll likely want to put a decent portion of this logic in your login Action.