This content has been marked as final.
Show 2 replies
-
1. Re: targetNamespace for remote webservice does not like jav
mylene Jun 21, 2006 5:21 AM (in response to evl123)The targetNamespace has java:com.name.etc
[wstools] java.lang.IllegalArgumentException: TargetNS should start with http/https/urn
This exception just tells you a targetNamespace (any namespace) should start with http, https or urn.
It cannot start with java...
This is not WS-I, SOAP or WSDL, but plain XML.
See for more information Namespaces in XML
Success,
Mylene -
2. Re: targetNamespace for remote webservice does not like jav
evl123 Jun 22, 2006 7:30 PM (in response to evl123)http https and urn are not the only available URI schemes
http://www.iana.org/assignments/uri-schemes.html
and xml namespace has no restriction on which ones to use.
http://www.w3.org/TR/REC-xml-names/
http://www.ietf.org/rfc/rfc2396.txt
so since its not in the XML+Namespace part then its got to be further up the standards stack. Either SOAP, WSDL or finally WS-I (which restricts further the SOAP and WSDL choices in favor of easier interoperability) or simply JBossWS itself has put in a restriction, though looking through the code I see it's actually JAXB recommendation that JBoss took to heart. So did JAXB get its ideas from a webservices restriction over XML or is JAXB imposing its own?