looks like wsdl4j that is included in the jbpm-console is not compatible with what you need to use in your work item handler. So you could try to upgrade the wsdl4j to the version you need.
Where you able to solve the problem?
I'm facing the same issue with my work item handler, i already checked in the gwt-console-server, the version of wsdl4j is 1.6.2.
That version has the method readWSDL(Ljavax/wsdl/xml/WSDLLocator;Lorg/w3c/dom/Element;)
I don't know what to do anymore.
Hope someone can help! Thanks!
This seems as a dependency issue only. You need to make sure that the dependencies don't crash, and unfortunately it is really difficult to help without having all the dependencies together. My suggestion for these cases is to make sure that you interact with the external web service using the dependencies that are already inside the jboss application service instead of adding your own libraries. That will definitely solve the problem.
Hi thanks for the answer!
I guess I'm not adding anymore dependencies.
In my pom I only have de jbpm dependencies and I use 2.4.4 cxf plugin to generate de classes from the wsdl.
Also, I'm only generating a workitem jar and adding in the lib folder of console-server war. I don't have any other war in the jboss except the ones that come with the jbpm installer.
It is very strange and I imagine it is something silly, but I cant put my finger on it :/
Well that could be the problem:
"In my pom I only have de jbpm dependencies and I use 2.4.4 cxf plugin to generate de classes from the wsdl."
Can you share your project so we can take a look? Take a look at the jboss version and which version of cxf is using that version. Maybe one of your generated proxies is different from the one that jboss is expecting.
JBPM 5.4 - gwt-console-server.war ->In lib folder, we have wsdl4j 1.6.2 (that jar contains the method required) and another jar javax.wsdl_1.5.1.v201012040544.jar, that also contains the same class, but does not contains de method required.
I removed the second one and it is working now.
I guess it was a mistake to have both jars together, however if a jbpm developer considers that I shouldnt remove it and the reason why, please let me now.
That sounds as a solution. Why do you end up with duplicated libs in there?
Really dont know, this war comes with de installer of jbpm.
But thanks for the help Salatino.