Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

RPC vs Document -Part element or type

 
Karthik Rajendiran
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Friends,I have a confusion regarding the role of part attribute in the SOAP BODY and message type too.

Let me begin with RPC literal where the
part tag inside message tag given with attribute type and element.
What would happen in soap body if type is given in rpc and element in rpc.
I have just given some example.

Example #1
<wsdl:message name="concatRequest">
<wsdl art name="concatRequestpart" type=�xsd:int� />
</wsdl:message>
<wsdl:message name="concatResponse">
<wsdl art name="concatResponsepart" type="xsd:string" />
</wsdl:message>
1. I feel in the rpc style, if we give part type as primitive xsd type, we get in the body as like part type=�xsd:int�
<concat >
<concatRequestpart> 5 </concatRequestpart>
</concat>
Response would be
<concatResponse> -�taken from message name attribute�s value
<concatResponsepart>SUSTAIN</ concatResponsepart>
</concatResponse>
Example#2
<xsd:complexType name=�concatRequest�>
<xsd:sequence>
<xsd:element name="s1" type="xsd:string"/>
<xsd:element name="s2" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<wsdl:message name="concatRequest">
<wsdl art name="concatRequestpart" type=�tns2:concatRequest� />
</wsdl:message>
<wsdl:message name="concatResponse">
<wsdl art name="concatResponsepart" type="xsd:string" />
</wsdl:message>


If for the same rpc style, I have used type, the body of the request
<concat>
<concatRequestpart>
<s1>kkk</s1>
<s2>sds</s2 >
<concatRequestpart>
</concat>
<concatResponse> -�taken from message name attribute�s value
<concatResponsepart>SUSTAIN</ concatResponsepart>
</concatResponse>
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic