ws-brsp message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [ws-brsp] Fw: Multiple inline schema's with the same targetNamespace doesn't work properly
- From: Doug Davis <dug@us.ibm.com>
- To: Jacques Durand <JDurand@us.fujitsu.com>
- Date: Wed, 5 Sep 2012 18:29:57 -0600
I've attached the docs I got from Gerwin.
If needed he said he can discuss the issue with the group if we wish,
but his company is not a member of oasis so he would need to be an invited
guest/expert or something like that I suspect.
thanks
-Doug
________________________________________________________
STSM | Standards Architect | IBM Software Group
(919) 254-6905 | IBM 444-6905 | dug@us.ibm.com
The more I'm around some people, the more I like my dog.
Jacques Durand <JDurand@us.fujitsu.com>
09/05/2012 06:43 PM
|
To
| Doug Davis/Raleigh/IBM@IBMUS, "ws-brsp@lists.oasis-open.org"
<ws-brsp@lists.oasis-open.org>
|
cc
|
|
Subject
| RE: [ws-brsp] Fw: Multiple inline schema's
with the same targetNamespace doesn't work properly |
|
We are talking of the very
first version of test tools (2003)…
So far I do not see in BP1.1
anything that prevents multiple
inline XSD Schema's with the same targetNamespace.
In fact, WSDL spec says: “There
can be multiple schemas associated with a particular namespace, and it
is up to a processor of XML to determine which one to use in a particular
processing context.”
The test assertions design
does not contain the error message Gerwin reports, so that seems to be
a message from the analyzer tool itself – a bug. An inspection of the
analyzer source code (developed by IBM?) would help.
We also miss the attachments
that were provided by original email.
Thx
-jacques
From: ws-brsp@lists.oasis-open.org
[mailto:ws-brsp@lists.oasis-open.org] On Behalf Of Doug Davis
Sent: Wednesday, September 05, 2012 1:08 PM
To: ws-brsp@lists.oasis-open.org
Subject: [ws-brsp] Fw: Multiple inline schema's with the same targetNamespace
doesn't work properly
Forwarding to the new group so that we don't forget that we owe Gerwin
an official response.
-Doug
---------- 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>
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:
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
Attachment:
Analyzer bug report.zip
Description: Zip archive
Attachment:
multischema.wsdl
Description: Binary data
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]