From: Jason S. <js...@in...> - 2011-02-22 16:45:50
|
Out of curiousity, how are you initially calling the XQuery? REST, XMLDB, XML:RPC, etc.??? eXist should not be shutting down as a result, it should handle the Java exception. But how it handles it depends, I believe, on how you have called the XQuery in the first place. Jason Smith ________________________________ From: Lauri Hyttinen [lau...@ho...] Sent: Tuesday, February 22, 2011 12:35 AM To: exi...@li... Subject: [Exist-development] Java exceptions crash the server Hello all, I have a java module inside exist doing various things and I've across some problems with it. Granted my java code is behaving badly and causing exceptions, which I am in the process of addressing but still I wonder whether eXist is behaving properly as well. My code causes an org.w3c.dom.DOMException with a HIERACHY REQUEST ERROR being the cause and this causes eXist to shut down. Earlier I had a null pointer exception which also caused the same effect. The null pointer exception is fixed and I am in the process of addressing the DOMException. But regardless of the exception is eXist supposed to shut down when a java module does these things? I know I have to write better java code :) but still it would be easier on the mind when I did not crash the server with my faulty java module. Best regards, Lauri Hyttinen |