[SWS-698] EndpointExceptionResolver is not registered automatically when used together with <sws:annotation-driven/> tag Created: 15/Mar/11  Updated: 04/May/12  Resolved: 22/Mar/11

Status: Closed
Project: Spring Web Services
Component/s: None
Affects Version/s: 2.0 GA
Fix Version/s: 2.0.1

Type: Bug Priority: Major
Reporter: Piotr Zielniok Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1h 40m
Original Estimate: Not Specified

Issue Links:
Relate
is related to SWS-682 ExceptionResolver order is reversed Closed
Reference URL: http://forum.springsource.org/showthread.php?p=351055&posted=1#post351055

 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.



 Comments   
Comment by Arjen Poutsma [ 22/Mar/11 ]

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

Comment by Arjen Poutsma [ 22/Mar/11 ]

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

Comment by Piotr Zielniok [ 24/Mar/11 ]

Works for me, Thanks!

Comment by Arjen Poutsma [ 29/Mar/11 ]

Corrected spelling in Summary

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Sat Dec 16 10:53:53 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.