[OPENEJB-965] http://www.nabble.com/exceptions-handling-with-Webservices-td19668275.html

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.7.0
• Fix Version/s: 3.1.2
• Component/s: webservices
• Environment: All
• Assignee: Jean-Louis Monteiro
• Reporter: Jean-Louis Monteiro
• Created: 01/Dec/08 13:57
• Updated: 02/Jun/14 20:01
• Resolved: 25/Sep/09 16:00

Description

As this problem becomes critical for applications, I have decided to open a JIRA.
The full description is available at http://www.nabble.com/exceptions-handling-with-Webservices-td19668275.html

Here are some thoughts.

In the intercept method of the EjbInterceptor class (openejb-cxf module), we can either directly call the target EJB bean (when no handler has been defined) or delegate to the CXF chain when handlers have been defined.

Regarding the first case, when an ApplicationException is thrown. This exception is caught by the preEjbInvoke method (from the EjbMethodInvoker). The preEjbInvoke method registers all exceptions as UNCHECKED so the client always receives a SOAPFaultException instead of the user defined application exception.

We can work around this problem by adding a dummy handler or change the test to be sure it's always false.

line 82: if (binding.getHandlerChain() == null || binding.getHandlerChain().isEmpty()) {

To conclude, invoking directly the target EJB bean does not handle exceptions correctly.