Raible's Wiki: IntegratingJBPMIntoAppFuse

At line 1 changed 1 line.

__Part I:__ [Integrating jBPM into AppFuse] - A HowTo for integrating jBPM Support (via Spring-Modules) into AppFuse.

__Part I:__ [Integrating jBPM into AppFuse] - Integrate jBPM Support (via Spring-Modules) into AppFuse.\\

__Part II:__ [Integrating jBPM into AppFuse Part Deux] - Setup AppFuse/jBPM in Eclipse, model defintions using the Jbpm Process Designer.\\

__Part III:__ [Integrating jBPM into AppFuse Part Trois] - Enhance defintions to support tasks, users, schedule and injecting spring beans into actions (Under Construction).\\

At line 4 changed 1 line.

This tutorial will show you how to configure jBPM 3.1 into AppFuse. It will also show you how to create process definitions and use them in the appfuse application context.

This is the 1st tutorial of a 3 part series. The tutorial covers how to configure [jBPM|http://www.jboss.com/products/jbpm] 3.1 into AppFuse. \\

At line 6 changed 1 line.

You will use the jbpm-db package to create the jbpm tables in your database for workflow persistence and will author process definitions in Eclispe. And finally you will write some [JUnit|http://www.junit.org] classes to test if the integration is working.

You will use the jbpm-db package to create the jbpm tables in your database for workflow persistence and will author process definitions in [Eclispe|http://www.eclipse.org]. And finally you will write some [JUnit|http://www.junit.org] classes to test the integration.

At line 8 changed 1 line.

AppFuse uses [Hibernate|http://www.hibernate.org] for its default persistence layer. jBPM also uses Hibernate for its persistence layer. It can be configured to either use the same session factory as Apppfuse or use its own dedicated session factory.

At line 149 changed 91 lines.

<list>

<value>org/jbpm/graph/action/Script.hbm.xml</value>

<value>org/jbpm/identity/User.hbm.xml</value>

<value>org/jbpm/identity/Group.hbm.xml</value>

<value>org/jbpm/identity/Membership.hbm.xml</value>

<value>org/jbpm/db/hibernate.queries.hbm.xml</value>

<value>org/jbpm/graph/def/ProcessDefinition.hbm.xml</value>

<value>org/jbpm/graph/def/Node.hbm.xml</value>

<value>org/jbpm/graph/def/Transition.hbm.xml</value>

<value>org/jbpm/graph/def/Event.hbm.xml</value>

<value>org/jbpm/graph/def/Action.hbm.xml</value>

<value>org/jbpm/graph/def/SuperState.hbm.xml</value>

<value>org/jbpm/graph/def/ExceptionHandler.hbm.xml</value>

<value>org/jbpm/instantiation/Delegation.hbm.xml</value>

<value>org/jbpm/graph/node/StartState.hbm.xml</value>

<value>org/jbpm/graph/node/EndState.hbm.xml</value>

<value>org/jbpm/graph/node/ProcessState.hbm.xml</value>

<value>org/jbpm/graph/node/Decision.hbm.xml</value>

<value>org/jbpm/graph/node/Fork.hbm.xml</value>

<value>org/jbpm/graph/node/Join.hbm.xml</value>

<value>org/jbpm/graph/node/State.hbm.xml</value>

<value>org/jbpm/graph/node/TaskNode.hbm.xml</value>

<value>org/jbpm/context/def/ContextDefinition.hbm.xml</value>

<value>org/jbpm/context/def/VariableAccess.hbm.xml</value>

<value>org/jbpm/taskmgmt/def/TaskMgmtDefinition.hbm.xml</value>

<value>org/jbpm/taskmgmt/def/Swimlane.hbm.xml</value>

<value>org/jbpm/taskmgmt/def/Task.hbm.xml</value>

<value>org/jbpm/taskmgmt/def/TaskController.hbm.xml</value>

<value>org/jbpm/module/def/ModuleDefinition.hbm.xml</value>

<value>org/jbpm/bytes/ByteArray.hbm.xml</value>

<value>org/jbpm/file/def/FileDefinition.hbm.xml</value>

<value>org/jbpm/scheduler/def/CreateTimerAction.hbm.xml</value>

<value>org/jbpm/scheduler/def/CancelTimerAction.hbm.xml</value>

<value>org/jbpm/graph/exe/Comment.hbm.xml</value>

<value>org/jbpm/graph/exe/ProcessInstance.hbm.xml</value>

<value>org/jbpm/graph/exe/Token.hbm.xml</value>

<value>org/jbpm/graph/exe/RuntimeAction.hbm.xml</value>

<value>org/jbpm/module/exe/ModuleInstance.hbm.xml</value>

<value>org/jbpm/context/exe/ContextInstance.hbm.xml</value>

<value>org/jbpm/context/exe/TokenVariableMap.hbm.xml</value>

<value>org/jbpm/context/exe/VariableInstance.hbm.xml</value>

<value>org/jbpm/context/exe/variableinstance/ByteArrayInstance.hbm.xml</value>

<value>org/jbpm/context/exe/variableinstance/DateInstance.hbm.xml</value>

<value>org/jbpm/context/exe/variableinstance/DoubleInstance.hbm.xml</value>

<value>org/jbpm/context/exe/variableinstance/HibernateLongInstance.hbm.xml</value>

<value>org/jbpm/context/exe/variableinstance/HibernateStringInstance.hbm.xml</value>

<value>org/jbpm/context/exe/variableinstance/LongInstance.hbm.xml</value>

<value>org/jbpm/context/exe/variableinstance/NullInstance.hbm.xml</value>

<value>org/jbpm/context/exe/variableinstance/StringInstance.hbm.xml</value>

<value>org/jbpm/msg/Message.hbm.xml</value>

<value>org/jbpm/msg/db/TextMessage.hbm.xml</value>

<value>org/jbpm/command/ExecuteActionCommand.hbm.xml</value>

<value>org/jbpm/command/ExecuteNodeCommand.hbm.xml</value>

<value>org/jbpm/command/SignalCommand.hbm.xml</value>

<value>org/jbpm/command/TaskInstanceEndCommand.hbm.xml</value>

<value>org/jbpm/taskmgmt/exe/TaskMgmtInstance.hbm.xml</value>

<value>org/jbpm/taskmgmt/exe/TaskInstance.hbm.xml</value>

<value>org/jbpm/taskmgmt/exe/PooledActor.hbm.xml</value>

<value>org/jbpm/taskmgmt/exe/SwimlaneInstance.hbm.xml</value>

<value>org/jbpm/scheduler/exe/Timer.hbm.xml</value>

<value>org/jbpm/logging/log/ProcessLog.hbm.xml</value>

<value>org/jbpm/logging/log/MessageLog.hbm.xml</value>

<value>org/jbpm/logging/log/CompositeLog.hbm.xml</value>

<value>org/jbpm/graph/log/ActionLog.hbm.xml</value>

<value>org/jbpm/graph/log/NodeLog.hbm.xml</value>

<value>org/jbpm/graph/log/ProcessInstanceCreateLog.hbm.xml</value>

<value>org/jbpm/graph/log/ProcessInstanceEndLog.hbm.xml</value>

<value>org/jbpm/graph/log/SignalLog.hbm.xml</value>

<value>org/jbpm/graph/log/TokenCreateLog.hbm.xml</value>

<value>org/jbpm/graph/log/TokenEndLog.hbm.xml</value>

<value>org/jbpm/graph/log/TransitionLog.hbm.xml</value>

<value>org/jbpm/context/log/VariableLog.hbm.xml</value>

<value>org/jbpm/context/log/VariableCreateLog.hbm.xml</value>

<value>org/jbpm/context/log/VariableDeleteLog.hbm.xml</value>

<value>org/jbpm/context/log/VariableUpdateLog.hbm.xml</value>

<value>org/jbpm/context/log/variableinstance/ByteArrayUpdateLog.hbm.xml</value>

<value>org/jbpm/context/log/variableinstance/DateUpdateLog.hbm.xml</value>

<value>org/jbpm/context/log/variableinstance/DoubleUpdateLog.hbm.xml</value>

<value>org/jbpm/context/log/variableinstance/HibernateLongUpdateLog.hbm.xml</value>

<value>org/jbpm/context/log/variableinstance/HibernateStringUpdateLog.hbm.xml</value>

<value>org/jbpm/context/log/variableinstance/LongUpdateLog.hbm.xml</value>

<value>org/jbpm/context/log/variableinstance/StringUpdateLog.hbm.xml</value>

<value>org/jbpm/taskmgmt/log/TaskLog.hbm.xml</value>

<value>org/jbpm/taskmgmt/log/TaskCreateLog.hbm.xml</value>

<value>org/jbpm/taskmgmt/log/TaskAssignLog.hbm.xml</value>

<value>org/jbpm/taskmgmt/log/TaskEndLog.hbm.xml</value>

<value>org/jbpm/taskmgmt/log/SwimlaneLog.hbm.xml</value>

<value>org/jbpm/taskmgmt/log/SwimlaneCreateLog.hbm.xml</value>

<value>org/jbpm/taskmgmt/log/SwimlaneAssignLog.hbm.xml</value>

</list>

<value>classpath*:/org/jbpm/**/*.hbm.xml</value>

At line 241 removed 6 lines.

<!-- The property below is commented out b/c it doesn't work when run via

Ant in Eclipse. It works fine for individual JUnit tests and in IDEA ??

<list><value>file:dist/appfuse-dao.jar</value></list>

</property>

-->

At line 276 removed 1 line.

Apparently there is another way to reference the mapping files(.hbm.xml) using "<value>org/jbpm/**/**/**.hbm.xml</value>" syntax, however, i couldn't get it to work.

At line 344 changed 2 lines.

A few words regarding the above code. We grab the config bean(previously configured) and use it to initialize a context. Using jBPM context we can make use of all the services defined in the jbpm.cfg file. GraphSession is used to load the latest instance of process definition. by executing an hql query (defined in org/jbpm/db/hibernate.queries.hbm.xml). Once we have the defintion we can create instances from that workflow and perform transition, tasks, adding variables, scheduling tasks etc (more on this later). So now its time to run this test case. The first time you fire up this test case, jbpm will initialize and deploy your process defintion to its database.

Infact everytime you start it up it deploys a new version of the defintion.

A few words regarding the above code. We grab the config bean(previously configured) and use it to initialize a context. Using jBPM context we can make use of all the services defined in the jbpm.cfg file. GraphSession is used to load the latest instance of process definition by executing a hql query (defined in org/jbpm/db/hibernate.queries.hbm.xml). Once we have the defintion we can create instances from that workflow and perform transitions, tasks, adding variables, scheduling etc (more on this later).

At line 347 changed 1 line.

In the next installment we will dive into creating more real-life like (tasks, variables, scheduling, custom queries) process defintions using the graphical plugin tool for Eclipse. We will also cover how to avoid reploying process defintions across server restarts, and finally we will inject some spring beans into our jBPM actions to demonstrate what a poweful and easy workflow mechanism jBPM really is!

The first time you fire up the test, jbpm will initialize and deploy your process defintion to its database. After it has been initialized you should get the green light of junit!

In the next installment we will setup appfuse/jbpm to run in Eclipse. We will also use Jbpm Process Designer to design defintions.

Raible's Wiki

AppFuse

Other Applications

IntegratingJBPMIntoAppFuse