Extending SoapFaultAnnotationExceptionResolver results in competing annotation resolvers with backwards order [SWS-793]

[gregturn]

Jonny Catlett opened SWS-793 and commented

I extended SoapFaultAnnotationExceptionResolver to create a custom exception resolver. While testing I realized that the default SoapFaultAnnotationExceptionResolver was handling the annotated exception being thrown. From the logs I could see that both resolvers were being created, and the custom one was never called.

I reverted back to version 2.0.1_RELEASE and the problem went away. It also appeared like the default SoapFaultAnnotationExceptionResolver was not created.

One workaround for this is to set the order of the custom resolver to highest priority, therefore delegating the exceptions to that resolver first, but this is not consistent with the documentation and samples.

---

Affects: 2.1 GA

Issue Links:

• SoapFaultMappingExceptionResolver not handling exception [SWS-777] #861 SoapFaultMappingExceptionResolver not handling exception
  ("duplicates")
• <sws:annotation-driven/> should register a SoapFaultAnnotationExceptionResolver [SWS-772] #857 sws:annotation-driven/ should register a SoapFaultAnnotationExceptionResolver

1 votes, 3 watchers

[gregturn]

Arjen Poutsma commented

This is due to #857. See my last comment on that issue for the reason.

As suggested, the workaround is to set an order on the exception resolver.