[JBoss jBPM] - JBPM 3 or 4
by tbeernot
Ok. JBPM 4 alpha is out. Compliments to the team!
But as a newcomer, I'm facing a decision now. I've just finished embedding jBMP 3.2.3 into our internal framework. I've solved all the issues and am ready to present it internally. Nothing has been done with it, apart from me writing unit tests.
I know jBPM 4 will have a new API, so I isolated all API code and I should be able to migrate fairly easy.
So just now I took a peek at jBPM 4 and noticed that the XML has changed seriously. And with that I'm less pleased, because the XML I cannot isolate! My user are supposed to write XML, using the designer or not.
My questions:
- Will jBPM 4.0 still be able to interprete the 3.2.3 XML process definitions?
- How stable is the 4.0 alpha? Can I migrate and demo?
- Is jBPM 4.0 getting along quickly enough to left me hold off on this until it is stable? (Are we talking weeks or months?)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201358#4201358
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201358
17 years, 2 months
[JBoss jBPM] - Re: ProcessInstance ending changed
by Olivier_Debels
Here is a unit test.
When aborting a child token, the child token is triggered to go to the next node (task node).
So we create an additional task instance. Something we certainly don't want when aborting the token.
public class AbortTokenTest {
|
| public static final String MAIN_PROCESS =
| "<process-definition name='MainProcess'>" +
| " <start-state>" +
| " <transition to='fork' />" +
| " </start-state>" +
| " <fork name='fork'>" +
| " <transition name='transition1' to='subProcess1' />" +
| " <transition name='transition2' to='subProcess2' />" +
| " </fork>" +
| " <process-state name='subProcess1'>" +
| " <sub-process name='SubProcess'/>" +
| " <transition to='taskNode1' />" +
| " </process-state>" +
| " <task-node name='taskNode1'>" +
| " <task name='generic' />" +
| " <transition to='join' />" +
| " </task-node>" +
| " <process-state name='subProcess2'>" +
| " <sub-process name='SubProcess'/>" +
| " <transition to='taskNode2' />" +
| " <task-node name='taskNode2'>" +
| " <task name='generic' />" +
| " <transition to='join' />" +
| " </task-node>" +
| " </process-state>" +
| " <join name='join' lock='UPGRADE'>" +
| " <transition to='end' />" +
| " </join>" +
| " <end-state name='end' />" +
| "</process-definition>";
|
| /**
| * Process definition with single root token and task node.
| */
| public static final String SUB_PROCESS =
| "<process-definition name='SubProcess'>" +
| " <start-state>" +
| " <transition to='taskNode' />" +
| " </start-state>" +
| " <task-node name='taskNode'>" +
| " <task name='generic' />" +
| " <transition to='end' />" +
| " </task-node>" +
| " <end-state name='end' />" +
| "</process-definition>";
|
| private JbpmContext jbpmContext;
|
| @Before
| public void initialize() {
| jbpmContext = JbpmConfiguration.getInstance().createJbpmContext();
|
| // Deploy sub process and main process
| jbpmContext.deployProcessDefinition(ProcessDefinition.parseXmlString(SUB_PROCESS));
| jbpmContext.deployProcessDefinition(ProcessDefinition.parseXmlString(MAIN_PROCESS));
| }
|
| @After
| public void uninitialize() {
| jbpmContext.close();
| }
|
| @Test
| public void cancelToken() {
| ProcessInstance processInstance = jbpmContext.newProcessInstance("MainProcess");
| processInstance.signal();
| assertNull(processInstance.getTaskMgmtInstance().getTaskInstances());
|
| // Abort one of the child token's
| processInstance.getRootToken().getChild("transition1").end(false);
|
| // Unit test fails -> a task instance is created in the main process
| // This because the child token is signalled and is in taskNode1 now...
| assertNull(processInstance.getTaskMgmtInstance().getTaskInstances());
| }
| }
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201344#4201344
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201344
17 years, 2 months
[JBoss jBPM] - Re: Workflow periodic execution and timers
by kukeltje
anonymous wrote :
| I would like to know if it's possible to have periodic execution of a certain workflow definition.
Yes
anonymous wrote :
| In case the answer is YES, and jBPM offers this scheduling functionality, could anyone point me in the right direction ?
|
jBPM does not offer this. Use e.g. quartz. jBPM 4 will most likely support this, but maybe not in the initial 4.0 release
anonymous wrote :
| I have tried to use timers (using the repeat property), but without too much success.
|
Timers with repeat work perfectly, just not for starting processes
anonymous wrote :
| Also I have been looking at the documents but I am having problems for using timers specifying an absolute value. Could anyone provide me a basic example where the basedate is defined ? I have been examples in the manual, but I am not able to find where dateOfPension (as an example) is defined, or how to define it (java code ? other configuration file ? in the bussines calendar config file??)
|
| <timer name="pensionReminder" duedate="#{dateOfPension} - 1 year" >...</timer>
dateOfPension is a processvariable, just like any other thing in EL (or a seam component if jBPM is used in seam)
anonymous wrote :
| Thanks.
| Jose.
|
You're welcome
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201135#4201135
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201135
17 years, 2 months