should we raise issues about these two points? And about logging? I'm still not able to make bpe log. The only log I get looks like a System.out because is not formatted and does not appear in outage.log.
bye Raffaele On Tue, 2006-03-28 at 20:17 +0200, Guillaume Nodet wrote: > The main problem is that the jbi endpoints wsdl is retrieved as a dom > document, so that there is no way to load external imports. The > errors are displayed by the container. I think the way to do this is > that the bpe component rewrites the wsdl with only the needed > informations (removing the imports), but that may not be always > possible, i guess. > These logs are warnings or debugs and should not affect your bpel > process (you won't be able to use interface routing however). > > This is one limitation currently. > The payload is another limitation. The bpe component does not have > access to the relevant informations and this is a hack so that > everything can work. > > Cheers, > Guillaume Nodet > > On 3/28/06, Raffaele Spazzoli <[EMAIL PROTECTED]> wrote: > > first of all thanks for the quick reply. > > I had a look at the demo and it is being useful. Thanks for the > > clarification so servicemix will have 2 BPEL SE. > > I did some step forward, and I'm stuck with an error again. I get the > > same error if I try to deploy the demo in servicemix distribution (I > > expect it to work if I use the directories prepared in the demo). > > The error is the following: > > WARN - EndpointRegistry.retrieveInterfacesFromDescription(250) | Error > > retrieving interfaces from service description: WSDLException > > (at /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: Unable to > > resolve imported document at 'CorbaEcho.wsdl'.: This file was not found: > > file:/home/raffaele/download/esb/servicemix-3.0-SNAPSHOT/CorbaEcho.wsdl > > DEBUG - EndpointRegistry.retrieveInterfacesFromDescription(252) | Error > > retrieving interfaces from service description > > WSDLException (at /wsdl:definitions/wsdl:import): faultCode=OTHER_ERROR: > > Unable to resolve imported document at 'CorbaEcho.wsdl'.: This file was > > not found: > > file:/home/raffaele/download/esb/servicemix-3.0-SNAPSHOT/CorbaEcho.wsdl: > > java.io.FileNotFoundException: This file was not found: > > file:/home/raffaele/download/esb/servicemix-3.0-SNAPSHOT/CorbaEcho.wsdl > > > > To me it means that bpe has succesfully imported the corba wsdl into the > > main wsdl, but the binding component is not able to do the same because > > it is doing it from the wrong relative path. I can of course work around > > the problem but I wanted to signal it > > > > Another question: why all the wsdl:part need have the name "payload"? > > bpe ives me an error if I try to use a different name. > > > > bye > > Raffaele > > > > On Tue, 2006-03-28 at 18:45 +0200, Guillaume Nodet wrote: > > > 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 > > > > > > > > > > > > > > > > > > > >
