Christopher Painter-Wakefield wrote:
> Since we upgraded to Cocoon 2.0.3, we've been experiencing a very annoying
> problem, which is that Cocoon seems to silently handle all exceptions.
> I've tested it now with a couple of exceptions types: RuntimeExceptions
> (thrown by the ESQL logicsheet) and NullPointerExceptions. The behavior is
> that we actually get back a page styled by our stylesheet, but with no
> data. Under C2.0.2, we'd get back a Cocoon error page complete with
> stacktrace. What's going on?
Dunno :-/
Have you tried outputting the xml of teh xsp and error without other
steps (remove all xslt also in handle-errors and put the xml serializer)?
What do you get?
> I looked at the new web.xml init-param "manage-exceptions", but changing it
> to false made things even worse - then I wouldn't even get XSP java compile
> error messages, just a generic internal server error message.
manage-exceptions=true should make Cocoon handle the exceptions, while
=false it gives them to the servlet engine.
> This problem (I won't say bug, in case it is something we've done!) is very
> detrimental to development, since we have to go look in the logs to find
> out we got an exception. Any help would be appreciated!
Please send us the page that is giving you problems, along with the
relevant log snippets, and anything that might help us to understand the
problem.
Thank you.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
