"camunda" wrote : You can set an "expected state" on the jbpm
SignalCommand. And I think if you get some really external signal, you need he
SignalCommand, or how do you want to get around this?
Unfortunately this is not sufficient to guarantee that the signal does not interfere with
the process flow.
"camunda" wrote : Returning the token id when starting a new process instance is
indeed an important use case where already some workarounds have been created because it
is not there! So I completly support this requirement.
Why token id and not process instance id?
"camunda" wrote : In this thread I think it is a good idea to mention again,
that the whole internals of the BpmProcessor are a bit, hmm, let's say hard to
understand... Best thing in my eyes is to rewrite it... I wanted to collect issues I have
with it but didn't had the time yet...
I completely agree. The BpmProcessor is overly complicated for what it needs to do and
could do with simplifying.
Kev
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199167#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...