Not yet, I've been trying to think of an elegant way of handling exceptions.
In a lot (most?) of cases you won't want to return a stack trace to the client;
instead a simple error code/message would be more useful. Whether this is
something that is done client side or server side I'm not sure. I'm leaning
toward server side because it would be nice to support I18N for error
messaging, and this way your error messages could be stored in a message bundle
resource.
As for how the message is handled on the client, I was thinking something along
the lines of allowing exception handlers to be registered at the method level,
e.g. Seam.Remoting.registerExceptionHandler("componentName", "componentMethod",
handlerMethod). Then your exception handler could do something graceful, like
display a 'Sorry the customer details could not be retrieved at this time'
message, etc.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950762#3950762
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3950762
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
