[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Fw: [wsrp] WSRP WSDL not currently conformant with WSDL 1.1 schem a
Claus, thanks for pointing this out. You are right. It is hard to find but to summerize (for my understanding): 1. WS-I R2754 is essential for us as it defines that wsdl:fault and soap:fault must have a matching value of their "name" attribute - currently we do not have this match 2. the schema given on the WSDL1.1 spec page, section A4 is not correct and there are inconsitencies between the spec and the schema posted on http://schemas... , as it defines the name attribute to be of type NMToken 3. the "correct" WSDL schema indeed defines the name attribute of wsdl:fault to be of type NCName 4. since 1. und 3. need to be met, we need to change the value of the name attribute of soap:fault like Claus proposed and Rich and I tried out on AXIS Mit freundlichen Gruessen / best regards, Richard Jacob ______________________________________________________ IBM Lab Boeblingen, Germany Dept.8288, WebSphere Portal Server Development Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888 Email: mailto:richard.jacob@de.ibm.com |---------+----------------------------> | | Richard | | | Jacob/Germany/IBM| | | @IBMDE | | | | | | 04/23/2003 02:08 | | | PM | |---------+----------------------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| | | | To: wsrp@lists.oasis-open.org | | cc: | | Subject: Fw: [wsrp] WSRP WSDL not currently conformant with WSDL 1.1 schem a | >--------------------------------------------------------------------------------------------------------------------------------------------------| Here is Claus von Riegen's contribution to our thread. Thanks Claus! Mit freundlichen Gruessen / best regards, Richard Jacob ______________________________________________________ IBM Lab Boeblingen, Germany Dept.8288, WebSphere Portal Server Development Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888 Email: mailto:richard.jacob@de.ibm.com ----- Forwarded by Richard Jacob/Germany/IBM on 04/23/2003 02:07 PM ----- |---------+----------------------------> | | "Von Riegen, | | | Claus" | | | <claus.von.riegen| | | @sap.com> | | | | | | 04/23/2003 01:57 | | | PM | |---------+----------------------------> > --------------------------------------------------------------------------------------------------------------------------------------------------| | | | To: Richard Jacob/Germany/IBM@IBMDE, wsrp@lists.oasis-open.org | | cc: | | Subject: RE: [wsrp] WSRP WSDL not currently conformant with WSDL 1.1 schem a | > --------------------------------------------------------------------------------------------------------------------------------------------------| Richard, One of the main drivers for WS-I in general and the Basic Profile 1.0 in particular was the need for a consistent interpretation and profiling of existing Web service specifications such as SOAP, WSDL and UDDI. As far as WSDL 1.1 is concerned, there are, for example, several inconsistencies between the specification (http://www.w3.org/TR/wsdl.html) and the XML schemas, which are available at http://schemas.xmlsoap.org/wsdl (WSDL 1.1 structure) and http://schemas.xmlsoap.org/wsdl/soap/ (WSDL 1.1 SOAP binding). One of these inconsistencies is actually the definition of the soap:fault element. While the specification defines the name attribute to be of type nmtoken, the schema defines it to be of type ncname. Regardless of its type, since the name attribute relates the soap:fault to the wsdl:fault defined for the operation, it must have the same value as the wsdl:fault anyway - and thus must omit the "intf:" prefix in the WSRP binding definitions. The WS-I Basic Profile Working Group agreed to use the WSDL schema definitions in this case. You can look up the corresponding resolution of the Basic Profile 1.0 at http://ws-i.org/Profiles/Basic/2003-03/BasicProfile-1.0-BdAD.html. The requirements R2028 and R2029 (see section 5.1.1) relate to the validness of WSDL documents in general, and the requirements R2721 and R2754 (see section 5.6.17) relate to the name attribute of soap:fault elements. Does this make sense? Best regards, Claus von Riegen, SAP -----Original Message----- From: Richard Jacob [mailto:richard.jacob@de.ibm.com] Sent: Mittwoch, 23. April 2003 13:01 To: wsrp@lists.oasis-open.org Subject: Re: [wsrp] WSRP WSDL not currently conformant with WSDL 1.1 schema I have tried the 0.95 and the proposed changes in 0.95 with AXIS1.1RC2 and could not find any relevant difference on the generated stubs and code, i.e. the messages sent over the wire would be the same. For me the change seems to be fine for consistency reasons. However, Yossi or Claus, could you point me to WS-I basic profile requirement stating this, I wasn't able to find this statement there. Or point me to the statement in the WSDL schema. What I found in the WSDL 1.1 spec for SOAP binding extensions: <definitions .... > <binding .... > <operation .... > <fault>* <soap:fault name="nmtoken" use="literal|encoded" encodingStyle="uri-list"? namespace ="uri"?> </fault> </operation> </binding> </definitions> Here the name is defined as being of type NMToken not NCName. And NMToken is defined as follows: Names and Tokens [4] NameCha :: Letter | Digit | '.' | '-' | '_' | ':' | CombiningChar r = | Extender [5] Name :: (Letter | '_' | ':') (NameChar)* = [6] Names :: Name (S Name)* = [7] Nmtoken :: (NameChar)+ = [8] Nmtoken :: Nmtoken (S Nmtoken)* s = This would mean that our definition is conformant, right? Mit freundlichen Gruessen / best regards, Richard Jacob ______________________________________________________ IBM Lab Boeblingen, Germany Dept.8288, WebSphere Portal Server Development Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888 Email: mailto:richard.jacob@de.ibm.com |---------+----------------------------> | | Rich | | | Thompson/Watson/I| | | BM@IBMUS | | | | | | 04/22/2003 08:36 | | | PM | |---------+----------------------------> > --------------------------------------------------------------------------------------------------------------------------------------------------| | | | To: wsrp@lists.oasis-open.org | | cc: | | Subject: Re: [wsrp] WSRP WSDL not currently conformant with WSDL 1.1 schema | > --------------------------------------------------------------------------------------------------------------------------------------------------| The axis tools I have installed on my machine are able to process the binding file with these removed. How about other tools? Rich Thompson "Tamari, Yossi" <yossi.tamari@sap.com> To: "'wsrp@lists.oasis-open.org'" <wsrp@lists.oasis-open.org> 04/22/2003 01:53 PM cc: "'andre.kramer@eu.citrix.com'" <andre.kramer@eu.citrix.com> Subject: [wsrp] WSRP WSDL not currently conformant with WSDL 1.1 schema Hi, Claus Von Riegen, who is a new observer of the WSRP from SAP and a WSDL and UDDI expert, had been running our WSDL through WS-I testing tools, which check for WSDL schema conformance. He found one minor problem regarding our definition of SOAP faults. Our WSDL uses qualified names to reference portType fault operations from soap:fault elements. Taking the following WSDL fragment (that is part of a wsdl:operation, which in turn is part of a wsdl:binding) as an example, <wsdl:fault name="AccessDenied"> <soap:fault name="intf:AccessDenied" use="literal"/> </wsdl:fault> The "intf:" prefix makes the WSDL document invalid against the WSDL 1.1 schema, since the soap:fault name attribute is of type NCName. Removing all occurrences of the "intf:" prefix should resolve the issue. I am sorry to raise this issue at such a late point, but I think that since fixing it is very simple and should not create controversy, and since it doesn't affect the spec itself, we can fix it without reopening the ballot... Yossi.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]