3 Replies Latest reply on Sep 6, 2010 6:10 AM by Pete Muir

    How to handle Weld exception at runtime?

    Wang Liyu Apprentice

      In the Weld, most of the exception are thrown from the listener, for example, the NonexistentConversationException, the question now is that how can we handle these exceptions more graceful?


      Some of the Exception really should be mute to the client browser (for example if conversation is not exist or timeout, should redirect to the default non-conversation page), I created a ExceptionProcessServlet and web.xml <error-page> session to get it work, but before the exception gets into the servlet, it logs the full stack on the backend which I really don't like, is there a better way to handle this? or should provide a session in the Weld document to talk about these problems?