[jboss-user] [JBoss jBPM] - Re: How to best control access from multiple threads to a Pr

kukeltje do-not-reply at jboss.com
Tue Dec 16 15:50:36 EST 2008

Guys.... please...... how does a random incomming message know how to signal the process? You clearly do not state that. You say just signal the process. Your example demonstrates that this is what you think you will do. What is the advantage of  having a process if any incoming message for that process instance can signal the process independent of the state it is in....

anonymous wrote : I had hoped that jBpm might have a clever way of achieving this without me having to write any code.It has, it's called the utopia feature.... now seriously... see my statement above. jBPM has no standard way to be able to service all different kinds of requirements. 

What you have to build is a component that knows the relation between a state/task/node and an incomming message (e.g. via a task-name<->xsd mapping). An incomming message should trigger that code to look up a task with the corresponding name and signal that *task*, not the processinstance.

anonymous wrote : Presumably in this case jBpm has some mechanism to prevent multiple actors fulfilling the task.
It has... it's called assigning a task to an actor. Sure, you can circumvent this if you use a low level api. There will not be an access violation or anything if another actor does it, but that means *your* application provided a way to achieve this.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196969#4196969

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4196969

More information about the jboss-user mailing list