Hi Frank,
Thanks for your time. In fact the 'errors' I expect are mostly
<bean:write> tags where the expected object cannot be found in any of
the scopes. I used to get those "javax.servlet.jsp.JspException: Cannot
find bean xyz in any scope" in my browser but since I switched to 1.2.x
they are all silent and I only see them in my Eclipse console. Which is
quite ok, but this is itching for some time now.
Could be I'm barking up the wrong tree here and forgot to define a
valve/logger/whatever in my context of overlooked some 'tinkering' at
another config file which accidentally slipped in all my new projects...
regards,
Martijn
Frank W. Zammetti wrote:
Hi Martijn,
Struts doesn't inherently do anything (that I'm aware of at least) to
stop JSP errors from being displayed in the browser... in fact it's
kind of unlikely it could since it's more or less out of the picture
by the time the JSP is executing (taglib code notwithstanding). Has
anything else changed that could cause this? Anything having to do
with JSP error page or something like that?
And, a slightly more pointed question :) ... are you sure the errors
you expect to see in the browser are really errors in the JSP?
Generally-speaking, runtime JSP errors are rare (they certainly should
be), and I'm assuming that's what we're talking about here rather than
compile-time errors.
--
31.69 nHz = once a year
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
