Re: [wsrp] WSRP WSDL not currently conformant with WSDL 1.1 schema

[Rich Thompson <richt2@us.ibm.com>]

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> 04/22/2003 01:53 PM

To:        "'wsrp@lists.oasis-open.org'" <wsrp@lists.oasis-open.org>         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.