[SWS-672] Allow MarshallingPayloadMethodProcessor to have a null marshaller or unmarshaller Created: 17/Dec/10  Updated: 04/May/12  Resolved: 20/Dec/10

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: 2.0 RC1
Fix Version/s: 2.0 RC2

Type: Improvement Priority: Major
Reporter: Josh Swan Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 17m
Original Estimate: Not Specified
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="...



 Comments   
Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

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