It will work if I try to put the XSD's in the directory mentioned. But then I will
have to put all the XSD's that my WSDL uses in that directory, which is not the
expected behavior
It creates problem later also when I try to create a WS Client for the deployed BPEL.
The error now will be like this
20:10:32,563 ERROR [[/jbpm-bpel]] jsp: could not read wsdl document
| javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema):
faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at
'Workflow1Dataschema.xsd', relative to
'http://192.168.1.97:8080/EnterpriseProcessManager/HumanTask/1224513534558eb75d24b5596a1b2_1f0dbaf5_11d1ab0258f_-7fff::Workflow1InvokeBatchMesh.wsdl'.:
java.io.IOException: Server returned HTTP response code: 500 for URL:
http://192.168.1.97:8080/EnterpriseProcessManager/HumanTask/Workflow1Data...
|
I actually did a work around for this and changed the import statements in the WSDL file
I made them to use the "location" instead of "schemaLocation". Then
the deployment worked, but I got error while building the the Web Module.
The error was something like this
error: modeler error: invalid entity name: "workflow1InvokeBM" (in namespace:
"http://www.altair.com/EPM/Workflow1Dataschema")
Any idea what this is? And the work around I did, is it a correct way. I got from some
googling only.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183262#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...