We originally decided to not go w/ BPEL as the core language, as we wanted to support all kinds of activities in a workflow, being able to make a workflow that mixes them. So it was planned that we'd get BPEL support, and allow you to incorporate BPEL into a regular Agila workflow using a namespace or something. Of course, we can decide if we want to change that plan here, but I think there are some compelling arguments for that kind of approach...
geir
On Oct 20, 2004, at 5:52 AM, Matthieu Riou wrote:
Hello,
I'm the project leader of Twister, an open source WS-BPEL engine. More can be found about Twister here:
http://www.smartcomps.org/twister
I'm sending this e-mail to suggest a donation of Twister to the Apache Group and a merge with the incubated Apache Agila project. I believe that Twister and the Gluecode engine could be assembled to a better solution, using the strengths of both implementations. This would also be beneficial for the BPM Open Source community and would bring more users and contributors to Agila.
Regards,
Matthieu Riou
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
