I've checked the pattern no 15 Wfp15MiWithAPrioriRuntimeKnowledgeTest in the
jbpm test source code. But the test case was built on the assumption that the
task instances are executes sequentially, one after another. In my case the
task instances can be executed concurrently.
Regards,
Martin
In my case actually the task instances (yes it's plural) can not be just
assigned to pooled actors because each of the actors will have their own task
instance of the same task. And the task has a task-end event that will change a
process instance variable whenever a task instance is finished. B
I have a Task node where a number of task instances are created and assigned to
mulpile actors. Each of these actors has his/her own task list page where they
can mark the task instance as finished. However whenever more than 1 actors
trying to finish the task instances, only 1 actor can actuall
Update :
The case where the log sequence is out of order only happens if I cancel the
task, but if I remove the task, the log is ok.
Now after playing around for a while with canceling and removing task
instances, I just found something that I really don't understand.
Base on the question no
Consider this example :
| "" +
| " " +
| "" +
| " " +
| " " +
| "" +
| " " +
| " " +
| "" +
| " " +
| "" +
| "" +
| " " +
| "" +
| " " +
| "" +
ups,sorry I incidentally hit the submit button before I finished typing :)
I mean there gotta be different meaning betwen putting all of them inside 1 row
|
| Name | Type|
Multiplicity
|
-
But if we can combine the usage of all the action, script, create-timer and
cancel-timer then why aren't they written into different row (in the doc) ?
Check out the doc about task (16.4.24). event, exception-handler, timer, and
controller are written inside different row in the doc so to me the
Excuse me for my (possibly) stupid question, but I'm confused on how to read
the user manual doc. In chapter 16. jpdl xml schema about event (16.4.14) it's
written
Name | Type | Multiplicity
-
Yeah, actually I write my code the same way as you do hosierdm. I haven't
tested the code inside appserver, only tested it using a swing base client.
What I notice is after I close the jbpmcontext object I can no longer use my
hibernate session because it already closed inside JbpmContext.close(
Hi,
I'm a newbe with this jbpm. I really hope I can get some help from the experts
here.
I'm confused about the usage of JbpmContext.
1. When exactly do we need to call JbpmConfiguration.createJbpmContext() vs
JbpmContext.getCurrentJbpmContext() ?
2. when do we need to close this JbpmContext o
10 matches
Mail list logo
