First, you may want to take a look at the bpel-pxe demo in the distribution (this one is only a few days old) if you have not already done so.
The bpe service engine has no documentation :( and may have a few bugs but i have successfully used it. It is not a substitution for pxe and I hope we will be able to reintegrate pxe once the LGPL dependencies have been removed, but we experienced some integration problems recently that are not solved yet (though some people have succeeded). You can download the sources at http://svn.apache.org/repos/asf/incubator/ode/scratch/ode/ The "Retrieving document at 'doubleecho'." message is not an import: it is displayed when loading the main wsdl. Your problem comes from a bad namespace in the bpel process for im prefix. The namespace has only one '/' instead of two. Cheers, Guillaume Nodet On 3/28/06, Raffaele Spazzoli <[EMAIL PROTECTED]> wrote: > I'm trying to produce a demo using the bpe service engine and I'm > encuntering a lot problems due mainly to my ignorance about BPEL and > lack of documentation of the ode project (at least on apache I didn' > find anything it seems that even the code is not online yet) and the bpe > binding component. > Do you think that the bpe service engine in mature enough to produce a > demo since it has recently sustituted the pxe engine? > I've understood that I need a .bpel that represents the process file and > a .wsdl with the same name that represents the process external > interface. I attach them both. > When I deploy the su I get the following error > <----------- error -----------------> > Retrieving document at 'doubleecho'. > Mar 28, 2006 5:50:06 PM org.apache.ode.bpe.util.BPException log > SEVERE: [DoubleEchoProcess] message type im:EchoResponse not found. Make > sure the WSDL has been imported and namespaces have been set up > consistently. > org.apache.ode.bpe.deployment.bpel.DeploymentException: > [DoubleEchoProcess] message type im:EchoResponse not found. Make sure > the WSDL has been imported and namespaces have been set up consistently. > at > org.apache.ode.bpe.deployment.bpel.BPELUtil.throwNewException(BPELUtil.java:45) > at > org.apache.ode.bpe.deployment.bpel.BPELWSDLVariable.<init>(BPELWSDLVariable.java:65) > at > org.apache.ode.bpe.deployment.bpel.BPELRepositoryHandler.buildVariable(BPELRepositoryHandler.java:302) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.apache.ode.bpe.deployment.bpel.BPELSAXHandler.startElement(BPELSAXHandler.java:105) > at > org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) > at > org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown > Source) > at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown > Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl > $FragmentContentDispatcher.dispatch(Unknown Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown > Source) > at org.apache.xerces.jaxp.SAXParserImpl > $JAXPSAXParser.parse(Unknown Source) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) > at > org.apache.ode.bpe.deployment.bpel.BPELParser.parseBPEL(BPELParser.java:95) > at > org.apache.ode.bpe.deployment.bpel.BPELDeploy.deployJar(BPELDeploy.java:177) > at > org.apache.ode.bpe.bped.unmanaged.BPELDeployerSLImpl.loadDefinition(BPELDeployerSLImpl.java:78) > at > org.apache.servicemix.bpe.BPEDeployer.deploy(BPEDeployer.java:84) > at > org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:87) > at > org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:68) > at > org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly(DeploymentService.java:526) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:257) > at org.apache.servicemix.jbi.framework.AutoDeploymentService > $2.run(AutoDeploymentService.java:507) > at > org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291) > at EDU.oswego.cs.dl.util.concurrent.PooledExecutor > $Worker.run(Unknown Source) > at java.lang.Thread.run(Thread.java:595) > [Fatal Error] :1:1: Content is not allowed in prolog. > <---------- error end -----------------> > > notice that the bpe component seem not to use commons logging. Anyway I > understand that it does not find im:EchoResponse, which should be > visible if the .wsdl had been loaded correctly. If I delete the variable > statement the su get deployed and it exposes the wsdl correctly. So I > guess that the bpe engine doesn't see the .wsdl while the binding > component does. Perhaps the log: Retrieving document at 'doubleecho'. > means that the bpe engine is trying to load doubleecho from .? relative > to what? and how did it decided to look for doubleecho? > > In synthesys: > 1. how can I get more log from bpe? > 2. how does bpe look for the correspondig wsdl given a .bpel? > > thanks > Raffaele > > >
