H?;
Im using tWebservice (Talend DI 5.1.1.r84309) on Advanced mode to call an active webservice. Im able to call the webservice without problem using SoapUi.. But on Talend i'm getting the error below:
Exception in component tWebService_1
java.lang.RuntimeException: java.net.MalformedURLException: no protocol: tmpTargetNamespace0
at org.apache.ws.commons.schema.resolver.DefaultURIResolver.resolveEntity(DefaultURIResolver.java:71)
at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:684)
at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:538)
at org.apache.ws.commons.schema.SchemaBuilder.handleSchemaElementChild(SchemaBuilder.java:1513)
at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:659)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:540)
at org.talend.webservice.helper.ServiceDiscoveryHelper.getSchemaCollection(ServiceDiscoveryHelper.java:360)
at org.talend.webservice.helper.ServiceDiscoveryHelper.init(ServiceDiscoveryHelper.java:130)
at org.talend.webservice.helper.ServiceDiscoveryHelper.<init>(ServiceDiscoveryHelper.java:90)
at org.talend.webservice.helper.ServiceInvokerHelper.<init>(ServiceInvokerHelper.java:98)
at myloyalty.copy_of_testws_0_1.Copy_of_testWs.tWebService_1Process(Copy_of_testWs.java:316)
at myloyalty.copy_of_testws_0_1.Copy_of_testWs.runJobInTOS(Copy_of_testWs.java:580)
at myloyalty.copy_of_testws_0_1.Copy_of_testWs.main(Copy_of_testWs.java:442)
Caused by: java.net.MalformedURLException: no protocol: tmpTargetNamespace0
at java.net.URL.<init>(URL.java:567)
at java.net.URL.<init>(URL.java:464)
at java.net.URL.<init>(URL.java:413)
at org.apache.ws.commons.schema.resolver.DefaultURIResolver.resolveEntity(DefaultURIResolver.java:67)
Hi Pedro; Our webservice is working on 5.0.2. The problem is with 5.1.1. I compared the generated files. It looks like on 5.1.1 Util_tWebService_1 is using "org.talend.webservice.helper.Utils" class. But on 5.0.2 it uses a generic named class generated on the same file. It looks like a bug to me but im not sure. Anything i can do to help ?