NEW ISSUE with WSDL Files (was RE: [regrep] FW: RIM 2.01 distribu tion)

["Munter, Joel D" <joel.d.munter@intel.com>]

Hi Sally, et al,

While the first issue that I had previously noted about the use of the
"xsd:" qualified namespace within Registry.wsdl has now been fixed, through
a re-validation of the proposed Normative WSDL files, I see that there are
additional problems present between Registry.wsdl and
RegistrySOAPBinding.wsdl.  WHILE THIS PROBLEM WAS PRESENT IN THE V2.0
VERSIONS OF THE WSDL FILES, THIS SHOULD BE TREATED AS A NEW ISSUE.  Due to
the first issue not being fixed, I did not see this before.

The elements, QueryManagerSoapBinding, and LifeCycleManagerSoapBinding are
defined in RegistrySOAPBinding.wsdl using element types defined in
Registry.wsdl without qualifying them with the correct namespace.

Within RegistrySOAPBinding.wsdl, the following are incorrect:
    <binding name="QueryManagerSoapBinding" type="tns:QueryManagerPortType">
    <binding name="LifeCycleManagerSoapBinding"
type="tns:LifeCycleManagerPortType">

This is because Registry.wsdl defines "tns:" with the following namespace
declaration:
    xmlns:tns="urn:oasis:names:tc:ebxml-regrep:services:wsdl:2.1" 

and RegistrySOAPBinding redefines the "tns:" qualifier with the following
namespace declaration: 
    xmlns:tns="urn:oasis:names:tc:ebxml-regrep:soapbinding:wsdl:2.1"  

As QueryManagerPortType and LifeCycleManagerPortType are defined within
Registry.wsdl, the same physical namespace must be used if those types are
referenced in subsequent files such as RegistrySOAPBinding.wsdl.

There are several alternatives for fixing this.  Through discussions with
our in-house WSDL expert, Pallavi Malu, we recommend that a new declaration
be made within RegistrySOAPBinding.wsdl and the qualifier for
QueryManagerPortType and LifeCycleManagerPortType in the binding element be
corrected as follows:

Add the following declaration to RegistrySOAPBinding.wsdl:
    xmlns:atns="urn:oasis:names:tc:ebxml-regrep:services:wsdl:2.1" 

Correct the binding definitions within RegistrySOAPBinding.wsdl to:
    <binding name="QueryManagerSoapBinding" 
		type="atns:QueryManagerPortType">
    <binding name="LifeCycleManagerSoapBinding" 
		type="atns:LifeCycleManagerPortType">

In the future, I strongly recommend that whoever posts the next versions of
the two WSDL files, that they please check it against a good WSDL Validation
tool before declaring that they are correct.  Some of the errors only show
up after predecessor errors are fixed.  This is an iterative process.  I had
provided a reference to a good validation tool before.  Here it is again:

	WSDL Validator Web Service - This is a simple yet 
	effective Web service that validates a WSDL document. 
	Call ValidateWSDL and pass it the WSDL document's 
	URL and you get back an auto-generated client proxy 
	in C# along with an error report. It runs wsdl.exe 
	on the server and sends you the output plus the 
	generated file.
	http://www.gotdotnet.com/services/wsdl/wsdlverify.asmx 

Joel

-----Original Message-----
From: Fuger, Sally [mailto:sfuger@aiag.org]
Sent: Wednesday, May 15, 2002 6:30 AM
To: regrep@lists.oasis-open.org
Subject: [regrep] FW: RIM 2.01 distribution

...
http://www.oasis-open.org/committees/regrep/documents/2.1/services/Registry.
wsdl 
http://www.oasis-open.org/committees/regrep/documents/2.1/services/RegistryS
OAPBinding.wsdl 
...