Jump to content

d3cadent

New Members
  • Posts

    1
  • Joined

  • Last visited

d3cadent's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. 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
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.