Also in my opinion is correct to rollback process logs but what if in one of the rolled
back nodes jbpm sends an email to an operator or a customer or, in general, triggers some
operation in external systems?
We can't say that in this case the code has never happened,
in other words,
code has never happened for jbpm but it did happened for some external systems (or even
worse people).
There could be situations where syncronization between jbpm and external world would be
lost so i think that what Camunda did is a must even because using an ESB gives not only
asyncronicity but protocol/transport failover as well.
Camunda, could you explain better how did you designed that special service that collects
log data where internal jbpm error occurs?
did you store that logs in the same table as other logs or in a separate location?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213810#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...