WebServiceTemplate problem when invoking oneway style services with marshalSendAndReceive [SWS-337]

[gregturn]

Luciano Montebove opened SWS-337 and commented

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.

---

Affects: 1.5

Referenced from: commits 0c1f86f

[gregturn]

Arjen Poutsma commented

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

[gregturn]

Luciano Montebove commented

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.

[gregturn]

Arjen Poutsma commented

Ok, that explains it. Reopening.

[gregturn]

Arjen Poutsma commented

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).

[gregturn]

Luciano Montebove commented

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 :-(

[gregturn]

Arjen Poutsma commented

Closing issues for 1.5.1