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

DefaultMethodEndpointAdapter: Allow custom MethodArgumentResolvers and MethodReturnValueHandler to be processed before the defaults

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.4.2
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            scoldwell Scott Coldwell
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: