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

          griff777 Piotr Zielniok created issue -
          arjen.poutsma Arjen Poutsma made changes -
          Field Original Value New Value
          Fix Version/s 2.0.1 [ 11810 ]
          Assignee Arjen Poutsma [ arjen.poutsma ]
          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).
          arjen.poutsma Arjen Poutsma made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          arjen.poutsma Arjen Poutsma logged work - 22/Mar/11 4:21 AM
          • Time Spent:
            1h 40m
             
            <No comment>
          arjen.poutsma Arjen Poutsma made changes -
          Remaining Estimate 0d [ 0 ]
          Time Spent 1h 40m [ 6000 ]
          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
          arjen.poutsma Arjen Poutsma made changes -
          Status In Progress [ 3 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          arjen.poutsma Arjen Poutsma made changes -
          Link This issue is related to SWS-682 [ SWS-682 ]
          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 -

          Corrected spelling in Summary

          Show
          arjen.poutsma Arjen Poutsma added a comment - Corrected spelling in Summary
          arjen.poutsma Arjen Poutsma made changes -
          Summary EndpointExceptionResolver is not registered autmaticaly when used togeter with <sws:annotation-driven/> tag EndpointExceptionResolver is not registered automatically when used together with <sws:annotation-driven/> tag
          Hide
          arjen.poutsma Arjen Poutsma added a comment -

          Closing old issues

          Show
          arjen.poutsma Arjen Poutsma added a comment - Closing old issues
          arjen.poutsma Arjen Poutsma made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open In Progress In Progress
          6d 19h 44m 1 Arjen Poutsma 22/Mar/11 2:40 AM
          In Progress In Progress Resolved Resolved
          1h 45m 1 Arjen Poutsma 22/Mar/11 4:26 AM
          Resolved Resolved Closed Closed
          409d 2h 37m 1 Arjen Poutsma 04/May/12 7:03 AM

            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