OpenWFE, an open source (BSD) workflow engine made its 1.7.2 release available. From now on, OpenWFE is entirely Maven2-built. OpenWFE 1.7.2 contains many bugfixes, has undergone thorough optimization, and is available as a Maven dependency. This release is a kind of 'stabilization' before further advancements, with, among them, an Atom 1.0 event dispatch mechanism between engines and participants (processes riding syndication). OpenWFE is very open as it's available under the BSD license (open source), features access libraries in Python, Ruby, C#, PHP, Pnuts and more (open to other applications and platforms) and its process definition language is easy to master (open, not arcane). The 'mavenization' makes the OpenWFE business process engine even more open and available for Java developers. Ruby developers are not left out as a port of OpenWFE as a Ruby workflow engine is under work. http://www.openwfe.org http://jmettraux.openwfe.org
- Posted by: John Mettraux
- Posted on: November 02 2006 12:35 EST
First, Congratulation! Second, can someone who used the two workflow engines give us a comparison between them? Thanks, William Zhu
can someone who used the two workflow engines give us a comparison between them?Here is small evaluation report. https://www.theserverside.com/news/thread.tss?thread_id=39006#200677 IMHO both engines are good. PS Congratulations to OpenWFE team. They done really interesting engine.
I'll do the shallow comparison : * License : jBpm is LGPL, OpenWFE is BSD * Concept : jBpm is based on something they named "graphical oriented programming", OpenWFE uses a process definition language with basic building blocks like 'participant', 'sequence' and 'concurrence', process calculus. * Audience : jBpm is targeted at Java developers, OpenWFE has a wider potential audience as it has many access libraries in various languages. * Backup : jBpm is a jBoss project. OpenWFE is an independent open source project. Best regards, John