You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Daniel Schleicher <sc...@googlemail.com> on 2009/10/11 20:54:01 UTC

Re: What Does a Process Really Need?

Hi Craig,
I think it helps when you create a file with the name of your bpel file,
plus the filename extension "deployed". E.g. helloWorl.deployed. This tells
ode, that the process is already deployed and it won't be recompiled.

Cheers,

Daniel

On Fri, Sep 25, 2009 at 4:52 PM, Craig Riecke <Cr...@cxtec.com> wrote:

> I have an SOA repository with lots of artifacts tucked neatly into
> subjects.  When I write a BPEL script, I import these and run bpelc on them.
>  That creates a compiled file *.cbp with all the artifacts in
> machine-digestible format.  Which is cool.
>
> My Ode server doesn't have access to the SOA repository.  But that
> shouldn't matter.  It seems like I should be able to copy the deploy.xml and
> the *.cbp file, right?  Unfortunately, in its default state, Ode looks for a
> .bpel file.  When I provide it, Ode tries to compile it, doesn't find the
> artifacts, and the usual chaos ensues.  So is there a way to say, "I've
> changed this process, but don't try to recompile anything." ?
>