"On a recent upgrade..." to what CXF or Spring version? Also, when are
you getting the message: after deployment of the web service endpoint,
making a client call, or running WSDL2Java?
Can you send us the world's smallest WSDL that duplicates the problem?
Glen
On 10/24/2012 04:19 PM, aehrensberger wrote:
We're currently using spring 3.1 with CXF 2.6.2. On a recent upgrade, our
WSDLs have all broken with the following message:
This page contains the following errors:
error on line 3 at column 77: xmlns:ns0: '##default' is not a valid URI
error on line 1608 at column 88: xmlns:tns: '##default' is not a valid URI
Below is a rendering of the page up to the first error.
Examining a previously working WSDL to the newly broken WSDL, I can view the
page source and recognize the issue, but I can't find any explanation as to
the cause or where to start looking.
The working wsdl line
<xs:schema attributeFormDefault="unqualified"
elementFormDefault="unqualified"
targetNamespace="http://www.docy.com/webservices/DocumentWebServices";
xmlns:ns1="com.docy.enums"
xmlns:tns="http://www.docy.com/webservices/DocumentWebServices";
xmlns:xs="http://www.w3.org/2001/XMLSchema";>
but the newly broken line appears as
<xs:schema attributeFormDefault="unqualified"
elementFormDefault="unqualified"
targetNamespace="http://www.docy.com/webservices/DocumentWebServices";
xmlns:ns0="##default" xmlns:ns1="com.docy.enums"
xmlns:tns="http://www.docy.com/webservices/DocumentWebServices";
xmlns:xs="http://www.w3.org/2001/XMLSchema";>
Notice the xmlns:ns0="##default" being added to that line. Why is there a
new one there and where did it come from?
Thanks for any help.
Aaron
--
View this message in context:
http://cxf.547215.n5.nabble.com/Upgrade-throws-strange-WSDL-error-xmlns-ns0-default-is-not-a-valid-URI-tp5717356.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
