axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bu...@us.ibm.com
Subject Re: WSDL specification
Date Fri, 30 Aug 2002 14:44:23 GMT
If you look at the latest version of javax.xml.namespace.QName, you'll see
that QName.toString returns "{<namespace>}<localPart>".  I suspect that
this is precisely for the reason that you present.

Russell Butek
butek@us.ibm.com


thomas.cherel@ascentialsoftware.com on 08/30/2002 09:22:51 AM

Please respond to axis-dev@xml.apache.org

To:    axis-dev@xml.apache.org
cc:
Subject:    WSDL specification





It might not be the best place to send this email, but I am trying to
understand the WSDL specification and I have a problem related to the
reference to a WSDL definition.

Section 2.1.1 of http://www.w3.org/TR/wsdl.html specifies that reference to
a WSDL definition is using a QName (basically something like NCName:
NCName). And I believe that the namespace prefix must point to the
namespace defined by the targetNamespace attribute of the wsdl:definitions
element. So far, so good.

My problem start to come from the fact that the name attribute for each
WSDL definitions (service, port, message, ...) is defined as being nmtoken.
According to XML specification, nmtoken can pretty much be anything
(including containing a ':'):

NameChar ::= Letter | Digit | '.' | '-' | '_' | ':' | CombiningChar |
Extender
Nmtoken ::= (NameChar)+

I was more expecting those name attributes to be NCName. What does it mean
to make a reference to a WSDL definition using a QName like
targetNamespace:nameAttributeValue if nameAttributeValue can also contain a
':'? Is it a real problem or since all that is not "real" XML namespace it
does not matter?

I am asking this question as we are currently working on a project where we
need to be able to analyze "any" WSDL files. I'd like to be as
interoperable as possible and obviously, being able to resolve the
reference to a WSDL definition is a big part of it.

Any help will be appreciated.

Thanks.

Thomas





Mime
View raw message