ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou" <matth...@offthelip.org>
Subject Re: Error parsing BPEL process
Date Wed, 21 Nov 2007 15:04:41 GMT
On Nov 21, 2007 5:58 AM, imorales <imorales@ignos.com> wrote:

>
> I found what was happening. The problem was that the ODE compiler try to
> compile all archives in the project with the extension .bpel and Maven
> created a directory with terminate in .bpel because maven places in
> META-INF/ some directories, in my case the directory of the groupId of my
> the project that end with .bpel :)
>
> I change the groupId of my project and solve the problem.
>

Ah if only Maven was better at supporting tar or zip archives! Anyway thanks
for looking into this, I'm going to add a little test to make sure the bpel
we find is actually a file and not a directory. Just in case...

Cheers,
Matthieu


>
>
> imorales wrote:
> >
> > Hi all, I´m using the jbi component apache ode-jbi 1.1 in ServiceMix
> 3.1.1
> > When Servicemix is trying to start I get next error when ode component
> is
> > compiling my bpel archive  that contains the process to execute.
> >
> >  error: [BpelParseErr] Error parsing BPEL process: the BPEL is either
> > malformed or is invalid.
> >         at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:321)
> >         at
> > org.apache.ode.store.DeploymentUnitDir.compile(DeploymentUnitDir.java
> :161)
> >         at
> > org.apache.ode.store.DeploymentUnitDir.compile(DeploymentUnitDir.java
> :125)
> >         at
> > org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:165)
> >         at
> > org.apache.ode.jbi.OdeServiceUnit.deploy(OdeServiceUnit.java:62)
> >         at org.apache.ode.jbi.OdeSUManager.deploy(OdeSUManager.java:60)
> >         at
> >
> org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly
> (DeploymentService.java:527)
> >         at
> > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(
> AutoDeploymentService.java:335)
> >         at
> >
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory
> (AutoDeploymentService.java:646)
> >         at
> > org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(
> AutoDeploymentService.java:62)
> >         at
> > org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(
> AutoDeploymentService.java:609)
> >         at java.util.TimerThread.mainLoop(Timer.java:512)
> >         at java.util.TimerThread.run(Timer.java:462)
> > Caused by: org.xml.sax.SAXParseException: Content is not allowed in
> > prolog.
> >         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> > Source)
> >         at
> > org.apache.ode.bpel.compiler.bom.BpelObjectFactory.parse(
> BpelObjectFactory.java:306)
> >         at org.apache.ode.bpel.compiler.BpelC.compile(BpelC.java:317)
> >         ... 12 more
> >
> > Any ideas? Thanks in advance.
> >
>
> --
> View this message in context:
> http://www.nabble.com/Error-parsing-BPEL-process-tf4849654.html#a13877657
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message