Hi Matthieu, Before you move the "virtual machine" into the ode trunk, Cory and I could use some help understanding the core engine. We are currently in the process of walking through the code but if someone from the PXE team could detail a few questions I think we could get there quicker. I think its great that you were able to get the forEach activity implemented in a week, however from an outsider looking in I find the implementation hard to follow and its taking us some time to walk through it. Here is where we could use some help ( i.e. sequence diagrams - etc .. ):
1) How does the Jacob engine walk the OModel? 2) How are messages/events correlated to an instance? 3) When you moved the parser/BOM into the trunk I asked as couple of questions and I think they may have fallen out of view. In particular I would like to understand the purpose of the BOM ( i.e. why not parse directly into the OModel )? Thanks, Lance On 5/10/06, Matthieu Riou <[EMAIL PROTECTED] > wrote:
Hi, In the process of building Ode block by block, I'd like to propose the import of the Jacob "virtual machine" in Ode's trunk. We've had a pretty long discussion about the different possible models (petri net vs pi-calculus) and even if probably both models are valid, we already have a very good implementation of a pi-calculus that we can use. As an example of its advantages, I've recently been able to implement the forEach BPEL 2.0 activity in less than a week (including testing and with only a bit more than a day spent on runtime). What do you think? Matthieu.
