Add support for ordering custom MethodArgumentResolvers and MethodReturnValueHandlers [SWS-1010]

[gregturn]

Scott Coldwell opened SWS-1010 and commented

Currently any custom resolvers or handlers added to DefaultMethodEndpointAdapter are added to the end of the corresponding lists. So when the supports or handle methods are called the custom ones provided are checked last. I think if someone is providing their own customized resolvers/handlers, they would want them checked first. In our case, the method parameters and return types we're using are supported by our own resolver/handler, but also by XmlRootElementPayloadMethodProcessor, but because ours are added to the end of the list, XmlRootElementPayloadMethodProcessor takes precedence and ours are never used.

We are working around this by extending WsConfigurationSupport instead of using @EnableWs and overriding the defaultMethodEndpointAdapter method to completely replace the default resolvers/handlers, but this seems like it shouldn't be necessary.

---

Affects: 2.4.2

1 votes, 2 watchers

[snicoll]

Good one. The current API is a bit weird indeed.