Changes between Version 18 and Version 19 of DPWS_API_NOTES


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

--

Legend:

Unmodified
Added
Removed
Modified
  • DPWS_API_NOTES

    v18 v19  
    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)]] 
     37[[Image(getListNamesRequest.png)]] 
    3838 
    3939The 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): 
     
    4242}}} 
    4343 
    44 [[Image(getListNamesResponse.png, 400px)]] 
     44[[Image(getListNamesResponse.png)]] 
    4545 
    4646The getListNamesResponse message comprises a <!GetListNamesReturn> element, with child elements containing the names of the lists available for inspection: 
     
    6464The 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 : 
    6565 
    66 [[Image(getListRequest.png, 400px)]] 
     66[[Image(getListRequest.png)]] 
    6767 
    6868Request: 
     
    7575Response: 
    7676 
    77 [[Image(getListResponse.png, 400px)]] 
     77[[Image(getListResponse.png)]] 
    7878 
    7979{{{