Which xml files are you refering to?
Carsten
Andre Juffer wrote:
Hi All,
I am testing a cocoon-based webapp. For this, I use the 'mvn jetty:run'.
This all works fine, unless there is an error in any of the underlying
XML files. For instance, if there is a minor error like missing an '>'
(implying invalid XML), which is just a typing error, jetty just hangs
up completely and ultimately gives an out of memory error exception. If
that is not the case, the only way to stop jetty is to manually kill the
process (on a Linux box). Is there a way to get rid of or change this
behavior. With cocoon 2.1.* (and tomcat), decent error message and stack
trace were returned so that could figure out the problem. This would be
the preferred behavior.
Thanks,
Andre
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Carsten Ziegeler
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
