Hiya. So whenever the container encounters a RuntimeException, it's wrapped and rethrown to the client as an EJBException. This behaviour can be overridden by annotating the RuntimeException with @ApplicationException.
But what about cases where the RuntimeException is not a custom one? Whenever a NullPointer, ArrayIndexOutOfBounds, etc is encountered, the container is rethrowing these as an EJBException to the client alone, silently swallowing the server error. I want to know if the server encounters an unchecked, undeclared exception in any of my service methods. Namely, I've configured Log4J to email me. Anyone have experience dealing with this? How do you address it? Can I globally catch these with an interceptor, run "logger.error()", and rethrow? Thanks. :) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998788#3998788 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998788 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
