[CXF-4940] CXF not (always) responding with the correct exception when working with an exception hierarchy

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.7.4
• Fix Version/s: 2.6.8, 2.7.5, 2.5.11, 3.0.0-milestone1
• Component/s: Core
• Estimated Complexity: Unknown
• Assignee: Freeman Yue Fang
• Reporter: David G
• Created: 03/Apr/13 16:38
• Updated: 14/Aug/13 15:50
• Resolved: 08/Apr/13 02:32

Description

Hi there,

For a webservice I'm currently building (java first), I have a few custom exceptions arranged in a hierarchy. In order to have them properly declared in the WSDL, I list all possible exceptions in the WebMethod declarations, not only the top ones. That is, if exceptions B->A, I declare :
@WebMethod
String helloWorld() throws A,B;

And it works, as far as the WSDL is concerned.
What doesn't work is that when requesting the service and raising a 'B' (child) exception, the response embeds an 'A' (parent) fault.

I seem to have narrowed down the culprit to org.apache.cxf.interceptor.FaultOutInterceptor.getFaultForClass(BindingOperationInfo,Class<?>), which stops at the first exception 'assignable to' the one actually raised. I 'patched' it locally to return the 'closest to the one raised', and it does the trick for me.

I hope an actual CXF contributor can take a look at this issue. I'm a beginner with CXF, and I might use it improperly. Please bear with me if that's the case