cancel
Showing results for 
Search instead for 
Did you mean: 

Error generating webservice client for SOAP PI WSDL file

0 Kudos

I created a PI integration flow with a SOAP receiver interface and in the beginning a simple SFTP sender interface.

Using the provided WSDL file from the integration builder in SOAP UI I can send a request to the SOAP interface and I receive a message in the SFTP output folder.

Now I want to generate in NWDS a webservice client for this PI service and I get always the following error:

Could not generate proxy

    com.sap.ide.jee.ws.common.runtime.Wsdl2JavaGeneratorException: Error during WSDL-to-Java generation

    at com.sap.ide.jee.ws.jee5.runtime.consumer.internal.impl.Wsdl2JavaGenerator.generateInternal(Wsdl2JavaGenerator.java:177)

    at com.sap.ide.jee.ws.jee5.runtime.consumer.internal.impl.Wsdl2JavaGenerator.generate(Wsdl2JavaGenerator.java:97)

    at com.sap.ide.jee.ws.jee5.runtime.consumer.internal.impl.Wsdl2JavaGenerator.generate(Wsdl2JavaGenerator.java:83)

    at com.sap.ide.jee.ws.common.core.consumer.ProxyGenerationCommand.doGeneration(ProxyGenerationCommand.java:47)

    at com.sap.ide.jee.ws.common.core.consumer.AbstractWsdl2JavaGenerationCmd.performGeneration(AbstractWsdl2JavaGenerationCmd.java:149)

    at com.sap.ide.jee.ws.common.core.consumer.AbstractWsdl2JavaGenerationCmd$1.run(AbstractWsdl2JavaGenerationCmd.java:110)

    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)

    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)

    at com.sap.ide.jee.ws.common.core.consumer.AbstractWsdl2JavaGenerationCmd.runInWorkspace(AbstractWsdl2JavaGenerationCmd.java:131)

    at com.sap.ide.jee.ws.common.core.consumer.AbstractWsdl2JavaGenerationCmd.doExecute(AbstractWsdl2JavaGenerationCmd.java:124)

    at com.sap.ide.jee.ws.common.core.consumer.ThreadAwareCommand$1.run(ThreadAwareCommand.java:56)

    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Schema processing problem. See nested exception for details.

    at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.processSchema(ProxyGeneratorNew.java:776)

    at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:332)

    at com.sap.ide.jee.ws.jee5.runtime.consumer.internal.impl.Wsdl2JavaGenerator.generateInternal(Wsdl2JavaGenerator.java:172)

    ... 11 more

    Caused by: com.sap.engine.services.webservices.jaxws.JaxbSchemaToJavaGenerationException: Could not generate Java classes for schema![WARNING] Are you trying to compile WSDL? Support for WSDL is experimental. You may enable it by using the -wsdl option.

    unknown location

   

    [ERROR] Property "Notify" is already defined. Use <jaxb:property> to resolve this conflict.

    line 104 of file:/C:/Users/christian.stein/AppData/Local/Temp/eclipse/.update/1446797390705/1446797390710/src/wsdl/de/metro/treasury/systems/tpc/dir/wsdl/TPCEventMonitoring_IN_TPCEventMonitoring_INService.wsdl

   

    [ERROR] The following location is relevant to the above error

    line 517 of file:/C:/Users/christian.stein/AppData/Local/Temp/eclipse/.update/1446797390705/1446797390710/src/wsdl/de/metro/treasury/systems/tpc/dir/wsdl/TPCEventMonitoring_IN_TPCEventMonitoring_INService.wsdl

   

   

    at com.sap.engine.services.webservices.jaxws.JaxbSchemaToJavaWrapper.schemaToJavaCompile(JaxbSchemaToJavaWrapper.java:204)

    at com.sap.engine.services.webservices.jaxws.JaxbSchemaToJavaWrapper.generateInternal(JaxbSchemaToJavaWrapper.java:270)

    at com.sap.engine.services.webservices.jaxws.JaxbSchemaToJavaWrapper.generate(JaxbSchemaToJavaWrapper.java:309)

    at com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.processSchema(ProxyGeneratorNew.java:768)

    ... 13 more

Any Idea ?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Christian,

Could you please provide details a little clearly..Its kinda confusing..Is is SFTP at sender end and SOAP at receiver? What is it that you are trying to test..

Thanks..

0 Kudos

Yes, The soap interface is the receiver at the beginning of the iFlow. It should receive a message from a scheduled job. This job creates a message which should be provided to the SOAP interface.

Currently I'm using the SFTP sender as output just to test the connection between the job and SOAP interface. So I can see if the message arrives and what's the content of the message.