How to handle Weld exception at runtime?

[wangliyu]

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?

[asiandub]

Jason Porter is currently developing a Seam 3 module around that issue:

http://github.com/LightGuard/seam-exception-handling

Maybe that's a source for some ideas

[wangliyu]

Thanks man, that's helpful, but it only address how to handle the exception but not how to catch the exception (actually I've done the same thing, just a simple version of that), so I still need to use servlet through the web.xml to catch the exceptions.

Actually I was thinking something more like JSF2 Exception Queue, so when there is a exception, Weld will enqueue it or event it, and my application can catch exception or observe the event and do some thing. Not sure if this is possible?

[pmuir]

This is what the extension that Jason is doing will do :-)