I'd put StripesFilter before it with it's mapping since StripesFilter is quite harmless.
Note that you should always make sure that DynamicMappingFilter is the last filter in the chain since it can break the chain. Christian -----Original Message----- From: Srini Nagul [mailto:[email protected]] Sent: Tuesday, March 10, 2009 1:58 PM To: [email protected] Subject: Re: [Stripes-dev] Calling Stripes action from Struts app Poitras Christian <Christian.Poitras <at> ircm.qc.ca> writes: > > Ok, I didn't explain that my actions don't point to .action since I > use URLBinding. > > Just remove this from web.xml: > <servlet-mapping> > <servlet-name>StripesDispatcher</servlet-name> > <url-pattern>*.action</url-pattern> > </servlet-mapping> > > I use this mapping only because of WaiPageInterceptor... Perfect! It works. Thanks a lot. Any ideas how to resolve the following commented snippet in web.xml earlier.Should I write a StripesActionBean and chain it ? LoginFilter basically extendes Spring's OncePerRequestFilter and ensures an object exists in session (say user is logged in) and supports 'deeplinking' of url-bookmarkings. I don't want to lose that functionality and not sure if I can reuse it now. Thanks Commented snippet in web-xml: ----------------------------- <!-- <filter-mapping> <filter-name>LoginFilter</filter-name> <url-pattern>*.jsp</url-pattern> </filter-mapping> --> ------------------------------------------------------------------------------ _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development ------------------------------------------------------------------------------ _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
