Hello,
I found this peculiar behavior.
If I have this configuration in web.xml
<filter-mapping>
<filter-name>StripesFilter</filter-name>
<servlet-name>StripesDispatcher</servlet-name>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>ERROR</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
In action classes, if I try to access StripesConfiguration, I get error
Something is trying to access the current Stripes configuration but
the current request was never routed through the StripesFilter! As a
result the
appropriate Configuration object cannot be located. Please take a
look at the exact URL in your browser's address bar and ensure that any
requests
to that URL will be filtered through the StripesFilter according to
the filter mappings in your web.xml.
If I remove INCLUDE dispatcher it works fine.
The reason I added it to web.xml is for error handling. I have jsp page
that has <jsp:include page="/PortalLogo.action" /> - if this action
produces runtime exception, it does not get caught by ExceptionHandler
directly (stripes filter is not in the right place on the stack and
runtime exception is caught by container).
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
