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

[gregturn]

Piotr Zielniok opened SWS-698 and commented

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.

---

Affects: 2.0 GA

Reference URL: http://forum.springsource.org/showthread.php?p=351055&posted=1#post351055

Issue Links:

• ExceptionResolver order is reversed [SWS-682] #782 ExceptionResolver order is reversed

Referenced from: commits 9eb37a7

[gregturn]

Arjen Poutsma commented

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

[gregturn]

Arjen Poutsma commented

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

[gregturn]

Piotr Zielniok commented

Works for me, Thanks!

[gregturn]

Arjen Poutsma commented

Corrected spelling in Summary

[gregturn]

Arjen Poutsma commented

Closing old issues