Changes between Version 17 and Version 18 of DPWS_API_NOTES


Ignore:
Timestamp:
25/08/10 11:44:29 (9 years ago)
Author:
sdonegan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DPWS_API_NOTES

    v17 v18  
    3535The DPWS relies on several lists of valid terms which are specific to the functionality of this service. The reason for using these 2 "helper" operations rather than encoding these valid terms as <xs:enumeration> in the schema part of the WSDL, is so that future modifications to the service need not necessarily require the modification of the WSDL (which can be incovenient for clients already developed around a particular release of the WSDL). The !GetListNames operation simply returns the names of these lists, which can then be used in a subsequent call to the !GetList operation. 
    3636 
     37[[Image(getListNamesRequest.png, 400px)]] 
     38 
    3739The WSDL document defines the !GetListNamesRequest message as an empty <!GetListNames> element, so the request message should look like this (omitting the SOAP Envelope & Body parent elements): 
    3840{{{ 
    3941<getListNames xmlns="http://ejb.revitalization.services.ndg/"/> 
    4042}}} 
     43 
     44[[Image(getListNamesResponse.png, 400px)]] 
     45 
    4146The getListNamesResponse message comprises a <!GetListNamesReturn> element, with child elements containing the names of the lists available for inspection: 
    4247{{{ 
     
    5964The contents of each of the lists named by the getListNames operation are accessible by invoking a call to the getList operation, with the name of the list as the single argument, encoded as a getListRequest message, as defined in the WSDL : 
    6065 
     66[[Image(getListRequest.png, 400px)]] 
     67 
    6168Request: 
    6269{{{ 
     
    6774 
    6875Response: 
     76 
     77[[Image(getListResponse.png, 400px)]] 
     78 
    6979{{{ 
    7080<ns1:getListResponse xmlns:ns1="http://ejb.revitalization.services.ndg/">