[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsdm] WS-ResourceProperties and .NET implementations
-----Original Message-----
From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]
Sent: Wednesday, February 25, 2004 8:43 PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] WS-ResourceProperties and .NET implementationsI have spent some time trying to see if the subj. could be implemented and it provides to be quite a challenge. Here are my findings that I wanted to share with the group and see if anyone else tried it with a better outcome.
#1
I'm not sure that the following is right[<xsd:element name="GetResourcePropertyResponse" type="xsd:anyType"/>]
This definition requires SOAP serializer to include xsi:type *of the element itself*. This definition contradicts what the specifications says. What the spec says it should be
[<GetResourcePropertyResponse><abc:property>value</abc:property></GetResourcePropertyResponse>]
According to the above element declaration, it will *always* be serialized as
[<GetResourcePropertyResponse xsi:type="whateverAbcPropertyType">value</GetResourcePropertyResponse>]
The response element should be declared as a container.
[
<xsd:element name="GetResourcePropertyResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:any minOccurs="0" maxOccurs="1" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
]#2
The following does not appear to be interoperable at all.[
<xsd:element name="GetMultipleResourcePropertiesRequest">
<xsd:simpleType>
<xsd:list itemType="xsd:QName" />
</xsd:simpleType>
</xsd:element>
]The simple type list definition is merely ignored and looks like this [System.Xml.XmlQualifiedName GetMultipleResourcePropertiesRequest] in the code.
We can, of course, wait until it is fixed by Microsoft, but I don't think we can, and so WS-ResourceProperties must be fixed. Following is one possibility.
[
<xsd:element name="GetMultipleResourcePropertiesRequest">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="qname" type="xsd:QName" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
]#3
[
<wsdl:types>
<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace=
"http://www.ibm.com/xmlns/stdwip/web-services/WS-ResourceProperties"><xsd:include schemaLocation=
"http://www-106.ibm.com/developerworks/webservices/library/ws-resource/WS-ResourceProperties.xsd"
/>
]Tools think that two definitions of the same namespace exist. Both this schema and the included schema define the same namespace.
Inlining schema in the WSDL of WS-ResourceProperties helps resolve this. Another approach is to xsd:import and introduce dummy namespace in WSDL types section.
-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]