Which workflow engine are we going to use, and why?

Robl kijkt mee...

I have been looking at the documentation and API for both frameworks. OSWorkFlow seems simple, though complete. jBPM is much more powerful and thus more complex.

I defined the following requirements for the API's, which have all been met by both frameworks: - allow custom actions - XML definition of the workflow - easilly trigger the transition from one state to another (e.g. through our event mechanism) - create custom actions - persisting state (in both cases, hibernate can be used)

Both frameworks seem equally capable of fulfilling our requirements, however, the OSWorkFlow community seems to have had it's best days. There hasn't been any activity for a year now.

Conclusion: We should focus on jBPM as our choice of framework, as we are much more likely to get support from the community for it than OSWorkFlow.

---

Small note: I have also taken a very brief look at Apache ODE, but it seems more WebService? oriented, which is most likely way too much for the goals we have.

Milestone Sprint_3 deleted