RE: [wsdm] [interop] Starting point & testing scenario

["Sedukhin, Igor S" <Igor.Sedukhin@ca.com>]

#2 is it for now, IMO. I just don't see it otherwise today. I guess in the interop document we will just say that there are no WSA headers necessary to access the properties.

At a later point we may discuss how to make many WSDM manageable resources visible via the same "URL" using EPR headers. I don't think we have discussed that yet and it may just drag on for a while.

On the WSDL point, I agenerally agree on the spirit of it, but not on the technical spect. Here is how. Interop document will include a statement that manageability endpoint must support all operations and propertties as defined in WSDM and two operations from WSRP. However, the WSDL of the manageability endpoint must be provided at the interop event as a starting point. Either you feed it to you tool or look at it and fetch the URL address, is entirely up to you.


-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788

-----Original Message-----
From: Murray, Bryan P. [mailto:bryan.murray@hp.com] 
Sent: Friday, March 26, 2004 1:08 PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] [interop] Starting point & testing scenario

Using WS-ResourceProperties has the interesting side-effect of making the WSDL document alone potentially insufficient to communicate with resources supported by the Web service.

There are 2 cases where the WSDL document may be sufficient:
1) An operation in the WSDL that returns an EndpointReference might offer a mechanism to locate already existing resources or to create new resources.
2) There is only 1 resource supported by the Web service and no SOAP
header(s) are required to identify that resource. Unfortunately, WSDL does not require that all SOAP headers be listed and so it may be necessary to send a message to test this case.

In the case of our WSDM interop example (WeatherStationManageability service), we do not have an operation that returns an EndpointReference, and it is not defined as to whether a SOAP header is required to identify the resource. In WSDM we also are not creating resources, but instead refer to fixed resources that already exist.

For these reasons, I think it may be necessary for managers to have an EndpointReference as a starting point.

Another thought: I think our goals are more around testing the interoperable exchange of messages and access to manageability information rather than the successful  runtime digestion of manageability WSDL. Our testing would be a little simpler if we all write manageability endpoints that match exactly the same manageability WSDL (except for the endpoint address) and managers start with only the EndpointReference. In this way the manager already knows what operations and properties are supported and can concentrate on sending requests and processing responses.

Comments?

Bryan

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.php.