In this project, I think I'm not getting the WebResult because JAX-WS has decided that the request and response types are the same and it can reuse the same object - but how do I get it to update that object with data from the response?

I finally found the key, and something you said in your question actually got me close to the answer:

I experimented with the names I was using for the various types, elements, message names, operations names, and such. I've successfully used JAX-WS on other projects, but in those cases it generated code with a and non-void return type named after the WebResult. However, when I run my app in debug mode, I can see each RequestType instance in the debugger variables view, but because RequestsType has an with RequestData or ResponseData, the latter is null and the RequestData is as I provided. When I call port.request( paramOne, paramTwo, requestList ), I can see that the SOAP request is sent to the server, which responds with a valid SOAP response: Holder = 'requestList', targetNamespace = '', mode = ) Holder = 'paramTwo', targetNamespace = '', mode = ) Public void = 'paramOne', targetNamespace = '', mode = ) * Generated source version: = 'requests', targetNamespace = '', className = 'requests', targetNamespace = '', className = '.RequestsType') * This class was generated by the JAX-WS RI. įor some reason, the code generated by wsimport has a void return, and the INOUT params don't seem to be updated when the response is received. I'm working with a client's WSDL file that uses the same element definition for the input and output messages, but I'm having trouble getting JAX-WS/JAXB to unmarshal the response.

Binding of isaac the void