Hi,
By the Namespaces in XML 1.0 (second edition) [1]:
[Definition: An XML namespace is identified by a URI reference [RFC3986];
element and attribute names may be placed in an XML namespace using the
mechanisms described in this specification. ]
By RFC3986 [2]:
URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ]
hier-part = "//" authority path-abempty
/ path-absolute
/ path-rootless
/ path-empty
URI-reference = URI / relative-ref
So # is a valid char for XML namespace.
I couldn't find the information about '{' or '}' in RFC3986. But RFC2396 [3]
says they are not allowed for URI.
Thanks,
Raymond
[1] http://www.w3.org/TR/REC-xml-names/
[2] http://www.rfc-editor.org/rfc/rfc3986.txt
[3] http://www.ietf.org/rfc/rfc2396.txt
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Saturday, November 17, 2007 9:38 AM
Subject: Re: Change the syntax for qname in
META-INF/services/org.apache.tuscany.sca.contribution.processor.StAXArtifactProcessor
[snip]
Raymond Feng wrote:
The spec case is slightly different as the syntax is
namespace#wsdl.xxx(...). We know the # before wsdl.xxx(...) is the
delimiter.
[snip]
2) # is valid character for namespace, using # as the delimiter could
lead
to conflict.
[snip]
Isn't there a problem then with wsdlElement="
http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)"?
Are you sure that '#' is allowed in a namespace URI? This deserves double
checking. What about '}'? My XSD validator seems happy with a namespace
like http://abc}def. If '}' is allowed you can't do {namespace}localName
either, right?
I'd suggest to double check the URI RFC and also research the XML-* specs
for standard ways to express QNames (other than namespace prefix
notation).
Also, I'm not sure I understand the code issue. Can't the call to
String.indexOf('#') just be changed to String.lastIndexOf('#')?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
