Glad to have you with us Matthieu. I agree with a lot of your assessment; BPEL is really only part of the discussion (as being one language for describing interactions with WSDL-based constructs) while service orchestration is the larger picture. In that regard, I can understand the transaction manager analaogy that was made elsewhere and inherently the relationship to the service bus.
When we built our orchestration implementation we referred to the full range of academically recognized workflow patterns that are a clearly a superset of BPEL - knowing that BPEL is but one means to describe orchestration in the context of WSDL. If we had started with BPEL, the language, for the source of our design patterns we would have had only a partial understanding of orchestration. Having said that, the BPEL use cases are clearly important. On 2/14/06, Matthieu Riou <[EMAIL PROTECTED]> wrote: > > > How about making a fresh start then... If the Agila people are > > interested, put out a call for any and all other implementations of BPEL > > that might be donated and build a larger community, mixing the best of > > anything that is donated to get the best BPEL engine and community we > can? > > I would be quite happy to contribute and help to build such a project. > BPEL is getting more and more momentum these days and bringing more > advanced code and more contributors would definitely be a nice thing. > > Matthieu Riou. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
