Well, I wouldn't retain simplicity as an important aspect in choosing a BPEL implementation core for Ode. Whatever solution we choose, the learning curve to such a thing is pretty steep anyway and many commiters will have to learn the nitty-gritty details of BPEL first. Beside there are many, many things to work on around the engine core.
So, as with any other project, contributors will start proposing patches on peripheral functionalities (like persistence, xpath or tools integration). Then, when they'll get more familiar with the code, they'll get a commiter access and will be able to start they'll start working on small improvements. And when they'll be familiar with the code and BPEL, they'll work on the core (btw you just need to understand the implementation style, not pi-calculus nor Turing). There's both learning and meritocracy involved here. I'm sorry that Cory and Lance have to spend so much time to understand PXE's core, there haven't been enough (almost none) explanation provided so far. However, now that I understand PXE much better (thanks to Maciej for his time), I can start documenting it if that would help. Cheers, Matthieu. On 5/11/06, Bill Flood <[EMAIL PROTECTED]> wrote:
The Ode charter was formed to implement BPEL, not solve a general process calculus problem (of which the latter is dubious in the context of the runtime as formerly asserted in well respected academic circles). If somebody wants to implement a general process engine or go beyond BPEL with all sorts of extensions, that probably belongs somewhere else. I don't want the community to need to understand process calculus to work on this project (or the theory of universal Turing machines for that matter) - because it is not entirely necessary in the narrow context of the implementation of Ode for BPEL. I prefer the BPE core for that reason alone - simplicity and focus to the BPEL runtime problem. The engine does precisely what it sets out to do in a straightforward manner, doesn't introduce extra overhead or concepts, and we can explain it in terms anyone familiar with BPEL can understand. Besides, it's documented. ;-)
