ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou" <matth...@offthelip.org>
Subject Re: Providing information available in deploy.xml programatically
Date Mon, 04 Feb 2008 15:39:57 GMT
Hi Luciano,

I think for Tuscany, what could make sense is the have your own process
store or a modified version of ours. The process store in ODE is what keep
track of all your deployments, triggers the compiler when a process must be
deployed and reads the deploy.xml to feed all these informations back to the
engine.

Ideally, deployments would be managed by Tuscany and you would implement the
store interface [1]. The only "tricky" part in there is tracking deployment
versions and the directories where these are on the disk. But I'd think that
you already have something similar in Tuscany to handle composites.

Let me know if you need more details and thanks for the good work.

Cheers,
Matthieu

[1]
http://svn.apache.org/repos/asf/ode/tags/APACHE_ODE_1.1.1/bpel-api/src/main/java/org/apache/ode/bpel/iapi/ProcessStore.java

On Feb 3, 2008 12:02 AM, Luciano Resende <luckbr1975@gmail.com> wrote:

> I'm working on integrating BPEL and SCA in Tuscany (we have a embedded
> ODE server), and was wondering if there is a way to avoid using the
> deploy.xml when deploying a BPEL process, and provide any necessary
> metadata information programatically, in my case with information from
> a SCA composite file or other SCA artifacts.
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
>

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