Hello Community,
I am trying to consume the soap web service BonitaSoft 7.10 but this is throwing me the following error:
java.lang.reflect.InvocationTargetException
org.bonitasoft.engine.bpm.connector.ConnectorExecutionException: USERNAME=install | org.bonitasoft.engine.core.connector.exception.SConnectorException: org.bonitasoft.engine.connector.exception.SConnectorException: java.util.concurrent.ExecutionException: org.bonitasoft.engine.connector.exception.SConnectorException: org.bonitasoft.engine.connector.ConnectorException: Exception trying to call remote webservice
Does Anyone know how I can fix this problem?
Hello
could you clarify the following, the provided information are not enough, more context is needed
- you are using Bonita 7.10? please provide environment details (exact Bonita version, OS, database, Studio or Bundle, ....)
- you have a process using a soap connector and you want to access to an external Soap Webservice? do you have more info about this webservice
- can you provide the whole stack trace?
Hi i am using Bonita studio 7.8 with windows OS,the h2 database for testing. The Webservice is created on my local machine with doNet framework.I use the wsdl to consume the Webservice in Bonita. I have testing the webservice in SoapUi and it work.
Hello
assuming you are using Bonita 7.8.4, the webservice connector bundled within the studio is version 1.1.1 (see https://github.com/bonitasoft/bonita-studio/blob/7.8.4/bundles/plugins/org.bonitasoft.studio.connectors/pom.xml#L278). If you use a custom version, please let us know.
According to the implementation of the webservice connector 1.1.1, when an exception occurs in the connector internals, the connector rethrows it as a ConnectorException with the message you provide "Exception trying to call remote webservice" and chains the original cause, see https://github.com/bonitasoft/bonita-connector-webservice/blob/1.1.1/src/main/java/org/bonitasoft/connectors/ws/SecureWSConnector.java#L208
So in the Bonita logs, you should see the root cause exception of the ws call issue. So, can you please provide the whole stack trace?