Could it be the mdb runs in the transaction created by jBPM? In that case the behaviour
you see may be slithgly explained. You signal the stateA in it's own node-enter, wich
is not advised.
If you can look into this, we can go further from there.
could you create a pd.xml with the classes and an mdb.jar so if needed we can try to
simulate? Maybe initially post the code of the mdb and the external service action
View the original post :
Reply to the post :