The first thing I'd do is turn up logging to 11 on s2, xwork, tiles, and ognl.
Not sure why the exception page would be hit w/ *no* exception but I could
imagine that there could be an exception after the page/response has been
written to... Is the 'right' page rendered *completely*?
Dave
stan
Scott, are you sure that you don't have error pages pointing to oops.jsp
in your web.xml file?
http://e-docs.bea.com/wls/docs81/webapp/web_xml.html#1017571
On my first S2 project, I had pointed my errors to an oops.jsp out of
habit. I was trying to use S2 tags in the error page and ran into the
s
I wish I could switch on a British accent here -- mine goes to eleven
already but the knobber is broken off. It was a crazy show at the Garden
where some bloke kept tell'n me to crank the bugger up.
Yeah, the right page and no exceptions yet the oops.jsp (with its S2 tags)
is being flagged for of
Hey Wes --
Good catch bro! I do have oops.jsp configured in my web.xml, however, I
don't see how an exception could bubble up to the container with this
configuration in my struts.xml
Scott
Wes Wannemacher wrote:
>
> Scott, are yo
You know, I wondered the same thing when it happened to me... I'm
guessing to make it worse, the behavior probably changes if you change
containers. Another thing to consider is that if your
"exceptionLogger" result is to be available in any action in your app,
global-results are only configured at
5 matches
Mail list logo
