d3cadent Posted March 8, 2013 Share Posted March 8, 2013 Dear Gurus, I need to write an application that can send and receive SOAP messages, following a WSDL specification supplied by a third party. I am a bit stuck of how to exactly follow it and remain functional. Here is a snippet from the WSDL: 01: <s:element name="SubscriptionRequestContainer"> 02: <s:complexType> 03: <s:sequence> 04: <s:element minOccurs="1" maxOccurs="1" name="SubscriptionRequest" type="tns:SubscriptionRequestItemCollection"> 05: <s:unique name="uniqueUnitId"> 06: <s:selector xpath="Add|Renew|Delete"/> 07: <s:field xpath="@UnitId"/> 08: </s:unique> 09: </s:element> 10: </s:sequence> 11: </s:complexType> 12: </s:element> 13: 14: <s:complexType name="SubscriptionRequestItemCollection"> 15: <s:sequence> 16: <s:element minOccurs="0" maxOccurs="unbounded" name="Add" type="tns:SubscriptionRequestAddItem" /> 17: <s:element minOccurs="0" maxOccurs="unbounded" name="Renew" type="tns:SubscriptionRequestRenewItem" /> 18: <s:element minOccurs="0" maxOccurs="unbounded" name="Delete" type="tns:SubscriptionRequestDeleteItem" /> 19: </s:sequence> 20: </s:complexType> I must admit I am new to WSDL. That's why I do not fully understand what lines 05 - 08 mean. It must be some definition of how to make sure the names of sections at the same hierarchical level are unique in the resulting SOAP request, thus they can be accessed independently, by name. Can someone help me interpret this definition and explain what the names of the resulting SubscriptionRequest entries should be? Could they be Activate@001, Activate@099, Renew@012 - or how to properly interpret lines 05-08 above? Big-big thanks in advance, Tom Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.