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

EndpointExceptionResolver is not registered automatically when used together with <sws:annotation-driven/> tag

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0 GA
    • Fix Version/s: 2.0.1
    • Component/s: None
    • Labels:
      None

      Description

      After removing <sws:annotation-driven/> EndpointExceptionResolver starts to work. Whats more - it looks like that <sws:annotation-driven/> tag is not needed as anotation based Endpoints works without it.
      Additional details in the Spring forum post.

        Issue Links

          Activity

          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          Closing old issues

          Show
          arjen.poutsma Arjen Poutsma added a comment - Closing old issues
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          Corrected spelling in Summary

          Show
          arjen.poutsma Arjen Poutsma added a comment - Corrected spelling in Summary
          Hide
          griff777 Piotr Zielniok added a comment -

          Works for me, Thanks!

          Show
          griff777 Piotr Zielniok added a comment - Works for me, Thanks!
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          This should be fixed now: the <sws:annotation-driven/> tag does not register any exception resolvers anymore. It used to, and thus overrided the defaults in SoapMessageDispatcher.properties and also disabled autodetected exception resolvers, which is what you ran into.

          Can you please try a snapshot (as of tonight) and see if it works for you? I'd like to push out a 2.0.1 release later this week, containing this fix.

          Cheers, Arjen

          Show
          arjen.poutsma Arjen Poutsma added a comment - This should be fixed now: the <sws:annotation-driven/> tag does not register any exception resolvers anymore. It used to, and thus overrided the defaults in SoapMessageDispatcher.properties and also disabled autodetected exception resolvers, which is what you ran into. Can you please try a snapshot (as of tonight) and see if it works for you? I'd like to push out a 2.0.1 release later this week, containing this fix. Cheers, Arjen
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          Indeed, annotation-based endpoints work without it, but the use of the XSD namespace will give you some extras (like marshaller autodetection, for isntance).

          Show
          arjen.poutsma Arjen Poutsma added a comment - Indeed, annotation-based endpoints work without it, but the use of the XSD namespace will give you some extras (like marshaller autodetection, for isntance).

            People

            • Assignee:
              arjen.poutsma Arjen Poutsma
              Reporter:
              griff777 Piotr Zielniok
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 1h 40m
                1h 40m