Samuel Santos wrote:
> It seems that the forward caused by the authentication is not routed
> through the Stripes filter (not passing through my LocalePicker).
> How can this annoying behavior be fixed?
[...]
> <filter-mapping>
> <filter-name>StripesSecurityFilter</filter-name>
> <url-pattern>*.jsp</url-pattern>
> <dispatcher>REQUEST</dispatcher>
> <dispatcher>INCLUDE</dispatcher>
> </filter-mapping>
I usually add a second mapping, specifically for the login pages:
<filter-mapping>
<filter-name>StripesSecurityFilter</filter-name>
<url-pattern>/WEB-INF/login.jsp</url-pattern>
<url-pattern>/WEB-INF/loginError.jsp</url-pattern>
<dispatcher>FORWARD</dispatcher>
</filter-mapping>
This mapping maps the filter to the login pages, as these are not a separate
request, but a forward after the server has intercepted the usual (request)
chain. I don't map the filter to other forwards, as then the filter chain has
already been invoked for the request.
I use it to use the Stripes layout component in my login pages as well, but
it also enables Stripes' language support.
Oscar
--
,-_ Envy plus rhetoric equals "social justice".
/() )
(__ ( -- Thomas Sowell
=/ ()
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
