Title: Message

Here you go. Attached.

I also had to fix

<wsdl:message name="SetResourcePropertiesResponse">

<wsdl:part name="SetResourcePropertiesResponse"

element="wsrp:SetResourcePropertiesResponse" />

</wsdl:message>

It was an empty message :).

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

------------------------------------------------------------------------------

From: Murray, Bryan P. [mailto:brya...@hp.com] Sent: Thursday, March 25, 2004 6:36 PM To: Sedukhin, Igor S; ws...@lists.oasis-open.org Subject: RE: [wsdm] WSRP WSDL for the Interop If we are changing the WS-RP WSDL/schema anyway, lets correct the spelling of the element name: SetResourcePropertiesResponse (it has an extra 'p' in the WSDL).

Bryan

-----Original Message----- From: Sedukhin, Igor S [mailto:Igor...@ca.com] Sent: Wednesday, March 24, 2004 8:28 PM To: ws...@lists.oasis-open.org Subject: [wsdm] WSRP WSDL for the Interop

Attached is the WS-ResourcePropeties WSDL fixed for the WSDM interop. <<WS-ResourceProperties.wsdl>>

Basically I took [1]http://www-106.ibm.com/developerworks/library/ws-resource/WS-ResourceProperties.wsdl and inlined the schema instead of <xsd:include>.

Then, also, to align the schema to the spec and make it work :) [2]http://www-106.ibm.com/developerworks/library/ws-resource/ws-resourceproperties.pdf I had to do the following:

1. in the WSDL <types><schema elementFormDefault="qualified" attributeFormDefault="unqualified". This was missing and WSDL did not work right with the tools.

2. Removed "Request" from the element endings to match what is in the spec. So now it is <xsd:element name="GetResourceProperty", for example.

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

References

Visible links 1.
http://www-106.ibm.com/developerworks/library/ws-resource/WS-ResourceProperties.wsdl 2.
http://www-106.ibm.com/developerworks/library/ws-resource/ws-resourceproperties.pdf