Hello,
I am hitting a problem that I cant quite understand.
My goal is to have StripesFilter on the stack ahead of ServletDispatcher so
that if <jsp:include src="bad.action/"> throws runtimeexception, I have a
chance to process runtime exception as oppose to having
ServletDispatcher.service logging it and then passing it ExceptionHandler.
Currently, I have stripesfilter configured as
<filter-mapping>
<filter-name>StripesFilter</filter-name>
<url-pattern>*.action</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<!--<dispatcher>INCLUDE</dispatcher> -->
</filter-mapping>
When I uncomment INCLUDE dispatcher, I am getting errors during processing of
layout tag that StripesRunTimeConfigurration is not available, even if there
are no exceptions in the app, which is surprising.
When INCLUDE dispatcher is commented out, everything works fine except for
the cases when Action forwards to jsp which is part of layout and also contains
jsp:include to another action that throws runtime exception - basically, I am
getting noise in the logs.
The flow is like this
http:/test.action forwards to jsp, which part of layout (which is part of
another layout) and also contains "jsp:include bad.action/>" that throws
runtime that gets to StripesFilter after ServletDispatcher servlet
if anyone have ideas why uncommenting INCLUDE causes such grief to stripes
and/or how to put StripesFilter ahead in such situations ahead on the stack,
please let me know.
thanks
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
