1:47 a.m.
Tobias Wittur [http://community.jboss.org/people/tob1as] created the discussion
"Difficulties Invoking Rule Task"
To view the discussion, visit: http://community.jboss.org/message/627082#627082
--------------------------------------------------------------
Hi,
I was trying to invoke a rule task within my process.
First, I took the example that was part of the unit test examples:
http://community.jboss.org/servlet/JiveServlet/showImage/2-627082-16997/C...
http://community.jboss.org/servlet/JiveServlet/downloadImage/2-627082-169...
The execution works fine.
I then added a human task node and a script task:
http://community.jboss.org/servlet/JiveServlet/showImage/2-627082-16998/C...
http://community.jboss.org/servlet/JiveServlet/downloadImage/2-627082-169...
Here, the script task prints a hello world, but then the process instance stops at the
rule task.
Does anyone know, why it is not running into the rule task? As I estimate, the rule task
node has to be active at the time the fireAllRules function is executed ?! But do I have
to manually fire that event everytime a rule has to be executed in a process?
The java looks as follows.
System.out.println("Loading process BPMN2-RuleTask.bpmn2");
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.add(ResourceFactory.newClassPathResource("junit/BPMN2-RuleTask.bpmn2"),
ResourceType.BPMN2);
kbuilder.add(ResourceFactory.newClassPathResource("junit/BPMN2-RuleTask.drl"),
ResourceType.DRL);
KnowledgeBase kbase = kbuilder.newKnowledgeBase();
StatefulKnowledgeSession ksession = createKnowledgeSession(kbase);
ksession.getWorkItemManager().registerWorkItemHandler(
"Human Task",
new WSHumanTaskHandler()
);
List<String> list = new ArrayList<String>();
ksession.setGlobal("list", list);
ProcessInstance processInstance = ksession.startProcess("RuleTask");
ksession.fireAllRules();
Best regards,
Tobias
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/627082#627082]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1:45 p.m.
New subject: [jBPM] - Re: Difficulties Invoking Rule Task
Mauricio Salatino [http://community.jboss.org/people/salaboy21] created the discussion
"Re: Difficulties Invoking Rule Task"
To view the discussion, visit: http://community.jboss.org/message/627166#627166
--------------------------------------------------------------
Hi Tobias,
Yes you are right, when you use Rule Tasks now you need to call fireAllRules. The behavior
of the Rule Tasks Nodes in the current version works as follow:
The rule task node will activate the ruleflow group that contains your rules. At that
point all the activated rules inside that group are elegible to fire. For that reason you
need to call fire all rules in order to fire the active rules. I'm trying to change
that behavior to call it automatically.
Cheers
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/627166#627166]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:41 p.m.
New subject: [jBPM] - Re: Difficulties Invoking Rule Task
Esteban Aliverti [http://community.jboss.org/people/eaa] created the discussion
"Re: Difficulties Invoking Rule Task"
To view the discussion, visit: http://community.jboss.org/message/627263#627263
--------------------------------------------------------------
The behavior of Rule Task is the one defined by Mauricio.
You have 2 options:
1. execute fireAllRules() manually. This could be very tricky because maybe you don't
know when or where you need to invoke it
2. have a separate thread running fireUntilHalt() in the ksession. For this, you need to
manually start a thread invoking fileUntilRun() in its run() method.
But the question is, why does the first example work but the second doesn't?
And the "problem" is because of the inclusion of an asynchornous node in your
process: the Human Task.
So, when you start your process, the execution reaches the Human Task, the task is created
in the HT Server and the execution control gets back to your code. At that point you are
executing the fireAllRules(). This fireAllRules() is not doing anything because there is
nothing to be fired. The Rule Task was never executed yet.
When you complete the HT, the process continues its execution and the Rule Task gets
invoked. Here you need to call fireAllRules() to continue with the execution of the
process.
Best Regards,
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/627263#627263]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
9:38 a.m.
New subject: [jBPM] - Re: Difficulties Invoking Rule Task
Tobias Wittur [http://community.jboss.org/people/tob1as] created the discussion
"Re: Difficulties Invoking Rule Task"
To view the discussion, visit: http://community.jboss.org/message/628413#628413
--------------------------------------------------------------
Thanks Esteban,
is there an example for case 2 somewhere? Since the rule engine is a key selling point for
jBPM, I would like to be able to present a working business rule task in my scenario. This
invocation of a rule task within a process flow however seems a bit awkward.
I would expect the process to just simply run in a rule task, do something and go on with
the process.
Another thing - not that I am trying to do it - but could the rules engine theoretically
be exchanged / how tightly coupled is jBPM with the rules engine?
Best regards,
Tobias
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/628413#628413]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4850
days inactive
4857
days old
3 comments
3 participants
participants (3)
-
Esteban Aliverti -
Mauricio Salatino
-
Tobias Wittur