[SWS-337] WebServiceTemplate problem when invoking oneway style services with marshalSendAndReceive Created: 21/Apr/08  Updated: 05/May/08  Resolved: 02/May/08

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: 1.5
Fix Version/s: 1.5.1

Type: Improvement Priority: Minor
Reporter: Luciano Montebove Assignee: Arjen Poutsma
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


With version 1.5 is now possible for oneway style services configure an endpoint bean in spring-ws-servlet.xml with only an unmarshaller as it doesn't request an unmarshaller.
The problem is that in WebServiceTemplate using marshalSendAndReceive configuration of a marshaller is stilI required why it should be optional to cleanly support this kind of services.

Comment by Arjen Poutsma [ 01/May/08 ]

If you specify a requestPayload on the marshalSendAndReceive() method, a Marshaller is required. If you pass null, it is not.

See http://static.springframework.org/spring-ws/site/xref/org/springframework/ws/client/core/WebServiceTemplate.html#292

Comment by Luciano Montebove [ 02/May/08 ]

Sorry, I generated a mistake with the problem description:
The problem is not the marshaller, as I will always use a requestPaylod in a oneway service (i.e. an event notification), but the unmarshaller.
I don't want to specify an unmarshaller in WebServiceTemplate for a service that will return only an HTTP 200 code as a response.

Comment by Arjen Poutsma [ 02/May/08 ]

Ok, that explains it. Reopening.

Comment by Arjen Poutsma [ 02/May/08 ]

I've written some additional unit tests, and I still can't reproduce this. An unmarshaller is only required when there is a response (indicated by a content-length > 0).

Comment by Luciano Montebove [ 04/May/08 ]

You are right.
I discovered, the problem was on my side.I invoked the oneway service through a custom Web Service Proxy that generates a default "OK result" soap body for oneway service (I don't know why).
I must pay more attention before opening an issue

Comment by Arjen Poutsma [ 05/May/08 ]

Closing issues for 1.5.1

Generated at Sat Oct 20 19:56:52 UTC 2018 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.