On Tue, May 20, 2008 at 2:12 PM, Mike Edwards < [EMAIL PROTECTED]> wrote:
> Luciano Resende wrote: > >> So, in the case where we replace the ODE Process Store module with one >> implemented by Tuscany, is this new module going to be responsible for >> handling all the versioning and matching a running process instance >> with the right BPEL process version ? >> >> Also, can the modules that handle deploy.xml and process store be >> implemented separately (e.g Tuscany would handle deploy.xml but still >> use ode process store module) ? >> >> Thanks >> Luciano >> > Luciano, > > My reading of Matthieu's note is that what is necessary is simply that > Tuscany must implement a ProcessConf class, rather than the whole process > store. That can be prepared entirely from information which Tuscany has to > hand, although as Matthieu points out, there are complex details within the > ProcessConf implementation that will require us to re-use some ODE modules > that compile the BPEL process file, but he says that doing that will not be > too hard ;-) > > With Tuscany, the Process Store is not needed since Tuscany has the Domain > configuration to drive things. > What mike says. I should just add that picking the right process version depending on what's already executing is handled by the runtime. The only thing that it will need is to know what is the definition for all the process versions that are still around (haven't been undeployed). You just need to keep these artifacts around and feed them to the engine (by calling register) as long as they're needed. If you want, I can code the method that compiles the BPEL file if you give me a signature that gets the file as parameter (I don't know how you would look it up in the filesystem). Cheers, Matthieu > > > Yours optimistically, > > Mike. >
