From: Shawn H. <sh...@xt...> - 2006-04-19 00:01:42
|
Hi Kent, Thanks for your quick reply. I have some prototype WSDLs generated for both document and rpc styles using mzData. Please let me know if you like to take a look at them. Thanks, Shawn -----Original Message----- From: Kent Laursen [mailto:Ken...@ge...]=20 Sent: Tuesday, April 18, 2006 7:53 PM To: Shawn Hu; chr...@eb... Cc: psi...@li... Subject: RE: Element vs. complexType - mzData schema issue with WSDL using RPC style Shawn, Thank you. You are correct, and this will be added into our requirements set. The need for mzData to fit into the SOA and Grid worlds has become poignant is recent months. Regards, Kent Laursen PSI-MS -----Original Message----- From: Shawn Hu [mailto:sh...@xt...]=20 Sent: Tuesday, April 18, 2006 3:24 PM To: Kent Laursen; chr...@eb... Cc: psi...@li... Subject: Element vs. complexType - mzData schema issue with WSDL using RPC style The following issue is based on an assumption that mzData supports Web service definition (WSDL) for mass spec data transaction.=20 After some testing on WSDLs using mzData.xsd, I found an issue with the schema regarding its root element. It seems that the current mzData.xsd does not support WSDL rpc message style.=20 There are two SOAP message styles defined in W3C WSDL specifications: "document" and "rpc". Basically if a WSDL is defined for a "document" style, a schema element should be specified. However if a WSDL is defined for "rpc" style, a schema complexType should be provided.=20 The current schema can only be used for "document" style Web service since it only has a root element but no global complexType for the root: <xs:element name=3D"mzData"> <xs:complexType> .... In order to use the schema for both "document" and "rpc" styles, the root element is better to be defined as: <xs:element name=3D"mzData" type=3D"mzDataType"/> <xs:complexType name=3D"mzDataType"> .... </xs:complexType> The syntax of the related WSDL definition is listed below:=20 * Document message: use <element> in <message> <wsdl:message> <wsdl:part name=3D".." element =3D"g1:mzData"> <wsdl:message> * RPC message: use <type> in <message> <wsdl:message> <wsdl:part name=3D".." type =3D"g1:mzDataType.."> <wsdl:message> Note: g1 is a prefix of the mzData targetNamespace. Thanks, Shawn Shawn Hu, Ph.D. Xtensible Solutions sh...@xt... |