Raible's Wiki: IntegratingJBPMIntoAppFusePartDeux

At line 86 changed 1 line.

We have already written a test case in the [previous article|#ref-IntegratingJBPMIntoAppFuse-4], So go ahead and create {{ProcessTest.java}} class under {{test/dao/org/appfuse/jbpm/dao}} and copy the code from the previous installment with the following modifications:\\

We have already written a test case in the [previous article|IntegratingJBPMIntoAppFuse], so go ahead and create {{ProcessTest.java}} class under {{test/dao/org/appfuse/jbpm/dao}} and copy the code from the previous installment with the following modifications:\\

At line 110 added 1 line.

At line 115 added 1 line.

At line 120 added 1 line.

At line 125 added 1 line.

At line 130 added 1 line.

At line 133 added 1 line.

At line 135 added 3 lines.

;:%%(color: blue)''For production usage it is not ideal to redeploy process definitions on startup. Once you have played around with your process defintion and are quite certain you are going to stick with it. You can apply the following patch to have the JbpmConfiguration not deploy a process definition every time you restart, rather have it redeployed only if the processdefinition.xml on the file system is out of sync with the database version''%%

Raible's Wiki

AppFuse

Other Applications

IntegratingJBPMIntoAppFusePartDeux