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

Allow MarshallingPayloadMethodProcessor to have a null marshaller or unmarshaller

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0 RC1
    • Fix Version/s: 2.0 RC2
    • Component/s: Core
    • Labels:
      None
    • Environment:
      Spring-ws 2.0.0-RC1, Java 5.0

      Description

      With Spring 2.0 I like how it allows you to configure different binding mechanisms and marshallers for the request and response to a single operation. In my case, I am using the @XPathParam configuration to parse the request to my operation and using a custom Stax marshaller for the response. Below is my custom marshaller configuration in my spring context file. As you can see below, I have no Unmarshaller configured on MarshallingPayloadMethodProcessor because I am not doing any unmarshalling in my service using the Unmarshaller interface. The issue is that MarshallingPayloadMethodProcessor requires both a marshaller and unmarshaller be set and will throw an exception if they are not both set.

      Would it possible to change the MarshallingPayloadMethodProcessor's validation logic so it only checks that at least a marshaller or an unmarshaller is set instead of always requiring both?

      <bean class="org.springframework.ws.server.endpoint.adapter.DefaultMethodEndpointAdapter">
      <property name="methodReturnValueHandlers">
      <list>
      <bean class="org.springframework.ws.server.endpoint.adapter.method.MarshallingPayloadMethodProcessor">
      <property name="marshaller" ref="pingMarshaller" />
      </bean>
      </list>
      </property>
      </bean>

      <bean id="pingMarshaller" class="...

        Activity

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            swanjr Josh Swan
          • Votes:
            0 Vote for this issue
            Watchers:
            0 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 - 17m
              17m