• Post Reply Bookmark Topic Watch Topic
  • New Topic

Generated SOAP request wraps the method arguments in an element named after the argument  RSS feed

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a question that can be illustrated by using this post from 2010. I will steal code from this post to try make myself clear.

The following section is copy-pasted from the other thread




The following section is my question

I am implementing an existing webservice into my company's system. By doing this I have gotten the wsdl from the service provider, and I generate code with them using cxf. The wsdl is (as far as I can tell) using the document/literal style, and I am telling cxf to use it i BARE (not wrapped) mode.

BUT, I have a problem. As you can see in the examples above, when the user calls the "addNums" method in either wrapped or bare style, the resulting soap-request has <ns2:addNums> wrapped around the arguments. The webservice that we are implementing does not want the method name included in the request. If I want to perform addNums, then I want the soap message to just contain the AddNums (the java object containing the numbers) part and NOT the addNums (the name of the operation) part.

Explained using different names. My service has an operation called findLocation, and this operation receives a LocationQuery object as a parameter.

Expected behavior:

Generated SOAP Request:

The resulting soap request should only contain the parameter.

Actual behavior
While now testing the program, I get a "multi wrapped" object.

Generated SOAP Request:


While performing an operation in java code, the resulting xml request contains the name of the operation called, while the service i'm implementing does not expect the operation name in the soap request.
This parrot is no more. It has ceased to be. Now it's a tiny ad:
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!