[
https://issues.jboss.org/browse/JBRULES-3069?page=com.atlassian.jira.plug...
]
Anton Litvinenko updated JBRULES-3069:
--------------------------------------
Description:
I have a process with 3 nodes: Action Node (writing to system.out) => Async Work Item
(makes request and then waits for async result - not blocking) => Action Node (writing
to system.out)
So, I experimented like this:
1. started the process, saw first system.out, saw making request
2. updated the process to have a different system.out at last action node, deployed it to
Guvnor, waited for KnowledgeAgent to pick it up
3. sent response to the process at Async Work Item -> saw *new* system.out at the last
node.
Some discussion is available here:
http://drools.46999.n3.nabble.com/Drools-Flow-5-1-Updating-a-process-defi...
was:
I have a process with 3 nodes: Action Node (writing to system.out) => Async Work Item
(makes request and then waits for async result - not blocking) => Action Node (writing
to system.out)
So, I experimented like this:
1. started the process, saw first system.out, saw making request
2. updated the process to have a different system.out at last action node, deployed it to
Guvnor, waited for KnowledgeAgent to pick it up
3. sent response to the process at Async Work Item -> saw *new* system.out at the last
node.
Some discussion is available here:
http://drools.46999.n3.nabble.com/Drools-Flow-5-1-Updating-a-process-defi...
fixed link to discussion in the mailing list
Upgrading definition of a persistent process instance causes it to
pick up the updated process definition
---------------------------------------------------------------------------------------------------------
Key: JBRULES-3069
URL:
https://issues.jboss.org/browse/JBRULES-3069
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Anton Litvinenko
Assignee: Mark Proctor
I have a process with 3 nodes: Action Node (writing to system.out) => Async Work Item
(makes request and then waits for async result - not blocking) => Action Node (writing
to system.out)
So, I experimented like this:
1. started the process, saw first system.out, saw making request
2. updated the process to have a different system.out at last action node, deployed it to
Guvnor, waited for KnowledgeAgent to pick it up
3. sent response to the process at Async Work Item -> saw *new* system.out at the last
node.
Some discussion is available here:
http://drools.46999.n3.nabble.com/Drools-Flow-5-1-Updating-a-process-defi...
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira