Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-793

Extending SoapFaultAnnotationExceptionResolver results in competing annotation resolvers with backwards order

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 2.1 GA
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Environment:
      Mac OSX (10.7.4), java version "1.7.0_05", Spring WS core version (2.1.0_RELEASE)

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                arjen.poutsma Arjen Poutsma
                Reporter:
                jonnycatlett Jonny Catlett
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: