Hi Aki,
I was able to reproduce the success you are getting.
when we use local wsdl file to create client it works with the
schemaLocation specification.
And with out that schemaLocation when using local wsdl file it shows proper
error message like below.
java.lang.RuntimeException: Error compiling schema from WSDL at
{C:\Users\Documents\Neela\CXF-TestProjects\view-source 172.20.85.141
NetStubs RpcEncoded.asmx wsdl.xml}:
undefined simple or complex type 'soapenc:Array'
but when I create the SOAP UI project mock service using that proper wsdl
with schemaLocation defined and try to access it via http url, it throws the
NAMESPACE_ERR.
so in my case it goes in side the !file check and calls serializeSchema and
it fails inside that. when we use local wsdl file it will skip this part,
that's why it works fine.
*DynamicClientFactory.java Line#485*
* if (!key.startsWith("file:") && !key.startsWith("jar:")) {*
XmlSchemaSerializer xser = new XmlSchemaSerializer();
xser.setExtReg(schemaCollection.getExtReg());
Document[] docs;
try {
*docs = xser.serializeSchema(schema, false);*
} catch (XmlSchemaSerializerException e) {
throw new RuntimeException(e);
}
.
.
.
I am not sure if I could provide a live wsdl url because the sample is a
.Net webservice.
I have attached the soapUI project with mock service. but the schemaLocation
shown in mockservice wsdl is auto generated and come different.
If you import the soapUI project to SoapUI and run the mockservice you can
access the service via
http://localhost:8080/?WSDL
Test-NameSpace-Err-soapui-project.xml
<http://cxf.547215.n5.nabble.com/file/n5744932/Test-NameSpace-Err-soapui-project.xml>
Thanks for your patience.
Thanks & Regards,
Neela
--
View this message in context:
http://cxf.547215.n5.nabble.com/NAMESPACE-ERR-with-DynamicClientFactory-createClient-tp5744708p5744932.html
Sent from the cxf-user mailing list archive at Nabble.com.
