[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2541) State of final node when worlflow contains "async node" but should be the same as without async node
[
https://jira.jboss.org/jira/browse/JBPM-2541?page=com.atlassian.jira.plug...
]
Christophe Lallement commented on JBPM-2541:
--------------------------------------------
Forgive me this my remarks are not clear.
I've an opened discussion at
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254798#....
What i mean is, When you run workflow with asynchronuous node
http://docs.jboss.org/jbpm/v4.0/userguide/html_single/#asynchronouscontin..., how can
we know if the workflow is completed or not ?
If i look at example provided into distrib, i can see that into example
/examples/src/org/jbpm/examples/end/state,
At end of workflow, we test result by invoking processInstance.getState(); (and result is
completed as indicate in workflow)
Now just modifiy a node of the workflow and set it the continue property to
"async"
Then run the example and you should have the same result as before ? and not the result of
getState() is already "async"
PS: I test it by introducing a state node with asyn continue (and process it with Job as
indicate into documentation )
State of final node when worlflow contains "async node" but
should be the same as without async node
----------------------------------------------------------------------------------------------------
Key: JBPM-2541
URL: https://jira.jboss.org/jira/browse/JBPM-2541
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: windows XP, java 1.6.
Run of distrib example.
Reporter: Christophe Lallement
when we use workflow without sync (default) node, the final state of wokflow is
"complete" (if we have en ter state "completed" on end node).
It works fine when we execute wokflow synchronously.
But when we change a node to set it at value "async":
1/ First we need to use a Job to change process a state node.
2/ The end value of the workflow is already "async"
It's very important because manipulation of workflow depend of nature of node in this
workflow.
What we do if version 1 of workflow has only sync node then version 2 has asyn node ?
I find it 's a shame to have 2 APIs to manipulate the workflow, this means knowing in
advance whether the nodes are synchronized or not.
Is there a way to avoid this ?
You can check this to test end value of distribution sample:
org.jbpm.examples.async.activity
Regards
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira