WfMOpen is a J2EE based implementation of a workflow facility workflow engine) as proposed by the Workflow Management Coalition (WfMC) and the Object Management Group (OMG).
...dedicated into Java open source projects
The Taverna project aims to provide a language and software tools to facilitate easy use of workflow and distributed compute technology within the eScience community. As a component of the EPSRC funded myGrid project, Taverna is available freely under the terms of the LGPL.
Bossa is a workflow engine written in Java. The engine is very fast and lightweight, uses a very expressive Petri net notation to define workflows, does not require a RDBMS and is very simple to use and to integrate with java applications.
The Imixs Open Source Project was created to promote the development of workflow technologies based on open software standards. Within the scope of this project, various technologies and procedures are published that allow and support the development of open, process-oriented workflow systems.
The project comprises the development of a framework to create workflow systems as well as a reference implementation based on the JEE standard. Additionally, the project includes the development of a graphic editor for creation and management of WorkflowModels within the Eclipse framework and also client frameworks to be build in user interfaces.
Bonita is a flexible cooperative workflow system, compliant to WfMC specifications, based on the workflow model proposed by the ECOO Team, which incorporates the anticipation of activities as a more flexible mechanism of workflow execution. Bonita is Open Source and is downloadable in LGPL License.
The Open for Business Workflow Engine is based on the WfMC and OMG spec; (See the related documents for information on these specs.) it is a member of the Services Framework, and is tightly integrated with the Entity Engine. It uses the entities found in entitymodel_workflow.XML for definition information and entitymode_workeffort for runtime storage. All changes to a process or activity are persisted real-time. Therefore, the engine does not run in a thread, it is simply a group of APIs and common objects which handle the flow. When a change to the workflow is made, the engine then processes that change. When finished, the engine returns. Hence, if the application does crash, or the system reboots, the workflow will continue right where it left off upon restart.
JawFlow is a Workflow Engine partially conformal to WfMC (www.wfmc.org) directives, completely written in Java using JMX technology. It understands XML Process Definition Language (XPDL) and can be customized using activities written in Java or in any scripting language supported by BSF
|Page 4 of 5|