//Why rpc/wrapped generated the same SOAP as doc/wrapped ?
It is because we have asked it to do so.
Using Parameter style as WRAPPED has wrapped parameter with operation name tag.
Normally in text books, we show Parameter Style as WRAPPED or BARE with Document type only.
document/literal wrapped combination is same as document/literal, but wraps the contents of the body in an element with the same name as
the web service method (just like RPC-style messages). This is what web services implemented in Java use by default.
Point to understand that RPC binding can also have WRAPPED parameter style. Infact, WRAPPED parameter is the default and only allowed
parameter style that we can use with RPC. Parameter style BARE is not allowed with RPC. That's way, in text books, RPC style is not shown associated to WRAPPED style.
For example -
We get error as
There are 3 attribute that you can specify with SOAPBinding.
a. style - this attribute defines the binding type - RPC or Document
b. use - Specifies how the data of the SOAP message is streamed and recognised/validated. For example- Literal means that the SOAP body follows an XML schema
, which is included in the web service's WSDL document. As long as the client has access to the WSDL, it knows exactly how each message is formatted.
This paramter can be LITERAL or ENCODED.
c. parameterStyle - Specifies how the method parameters, which correspond to message parts in a WSDL contract, are placed into the SOAP message body.
A parameter style of BARE means that each parameter is placed into the message body as a child element of the message root.
A parameter style of WRAPPED means that all of the input parameters are wrapped into a single element on a request message and that all of
the output parameters are wrapped into a single element in the response message.
Oracle Java Web Service Developer (1z0-897), Oracle certified Java 7 Programmer, SCJA 1.0, SCJP 5.0, SCWCD 5.0, Oracle SQL Fundamentals I