---------- Forwarded message ----------
From: Gerwin Jansen <gjansen@cordys.com>
Date: Mon, Jun 4, 2012 at 10:55 AM
Subject: Multiple inline schema's with the same targetNamespace doesn't work properly
To: Scott McGrath <scott.mcgrath@oasis-open.org>
From: Gerwin Jansen <gjansen@cordys.com>
Date: Mon, Jun 4, 2012 at 10:55 AM
Subject: Multiple inline schema's with the same targetNamespace doesn't work properly
To: Scott McGrath <scott.mcgrath@oasis-open.org>
Hi WS-I members,
I created a WSDL with multiple inline schema's with the same targetNamespace. WSDL 1.1 is not very clear regarding this, but this is corrected in WSDL 2.0, which explicitly allows this:
I created a WSDL with multiple inline schema's with the same targetNamespace. WSDL 1.1 is not very clear regarding this, but this is corrected in WSDL 2.0, which explicitly allows this:
A WSDL 2.0 document may define multiple inline schemas in its types element. The two or more schemas may have the same target namespace provided that they do not define the same elements or types. It is an error to define the same element or type more than once, even if the definitions are identical.
This gives me the impression that WSDL 1.1 was also intended to allow this, although not explicitly stated.
Basic Profile Version 1.1 doesn't seem to restrict WSDL 1.1 in any way regarding multiple schema's with the same targetNamespace.
This is also confirmed by the fact that the Analyzer tool allows me to refer to different inline XSD Schema's with the same targetNamespace from a Message Part element.
But when it comes to a reference from one inline XSD Schema to another XSD Schema, it is failing saying:
Error: src-resolve: Cannot resolve the name 'same:addressElement' to a(n) 'element declaration' component.
I included the required Analyzer config file, WSDL file, console output and report in the attached zip file.
Given this scenario, I have the following questions:
1) Are multiple inline XSD Schema's with the same targetNamespace allowed? Are there any references available?
2) Can you confirm that the problem reported above is a bug in the Analyzer? If this is true, we can still claim to be Basic Profile compliant.
3) If this is a bug, can it be fixed?
Kind regards,
Gerwin
Gerwin Jansen | |
|
Scott McGrath
COO
scott.mcgrath@oasis-open.org
Tel +1 781-425-5073 x202
Fax +1 781-425-5072
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open