1.obes
Introduction: Follow WFMC defined workflow engine
Advantages: Support WFMC defined workflow interface specification, project developers are also more
Disadvantages: Persistence of workflow instances, lack of graphic editing environments, have not completed the five types of interfaces defined by WFMC
http://www.openbusinessENGINE.ORG/index.html
2.Ofbiz
Introduction: OFBIZ itself is a set of independent and complete enterprise application frameworks, including usual universal middleware and logical middleware in some areas.
Off is the most famous of its entity engine and service engine, and it also provides a rule engine and a workflow engine.
Advantages: physical engine and service engine, flexible and powerful, based on its workflow engine is also good. The use case is more, and the reference document is rich.
Disadvantages: huge, not a separate workflow engine.
http://www.ofbiz.org/
3.werkflow
Introduction: This workflow engine is based on status and procedure, dedicated to business integration and user interaction, fully uses hierarchical and plug-in ideas, and it is easy to use other components.
Advantages: good scalability, ideas based on executable XML scripts
Disadvantages: Update is not timely, lack of specifications
http://werkflow.codehaus.org/
4.Sworkflow
Introduction: Very flexible workflow engine, completely based on plugin ideas, extremely scalable, based on state.
Advantages: The workflow engine can work in JSP Container, EJB Container, WS Container.
The engine supports auto tasks and manual tasks.
Workflow instances and related data can be persisted, and JDBC, EJB, Hibernate, and other persistence methods can be selected.
Has a workflow scriptogram editor.
Various functions are based on plug-in, easy to integrate existing systems.
Workflow can call Java, EJB, Bean Shell, BSF, etc.
Support permission.
Timed task scheduling.
Suitable for web and non-Web environments.
Disadvantages: Non-standard scripting languages, workflow engines are not perfect for automatic task support.
http://wiki.opensymphony.com/space/osworkflow/
5.jbpm
Summary: Based on the workflow engine of JBoss EJB.
Advantages: Easy to install, support dynamic deployment, workflow engine supports the script of the interactive interface, for the web environment.
Disadvantages: The combination of JBoss and EJB is too close, not convenient for separation.
http://www.jbpm.org
6.bonita
Introduction: Very small workflow engine
Advantages: Based on Petrinet Model, it is easy to support theoretical analysis, support for persistence
Disadvantages: too simple, only suitable for research analysis workflow
http://bonita.debian-sf.Objectweb.org/
7. Other related items
7.1 Apache-Commons-Jelly
Its core thinking is "Executable XML", suitable for use when writing a workflow engine.
http://jakarta.apache.org/commons/jelly/index.html
7.2 blissid
Jelly based workflow basic components.
http://blissed.codehaus.org/index.html
7.3 JSR 207
JSR 207 - Process Definition for Javatm
I don't know if there is a standard implementation.
7.4 LenyaWorkflow
Very abstract theory, formal description
http://wiki.cocoondev.org/wiki.jsp?page=lenyaworkflow7.5 struts Workflow Extension
Struts-based page jump controller
http://www.livingLogic.de/struts/introduction.html
7.6 TAVERNA
The workflow in the grid project is committed to integrated distributed computing environment, scripting specification, engine, and editor.
http://taverna.sourceforge.net/
