exception handlers indeed don't solve your scenario since you're right that they
happen inside of the transaction.
i think this is out of scope for jBPM. the client controls the transaction (either
through hibernate in standard java or through JTA in enterprise).
In enterprise environments, you could use a Synchronization, no ?
in the POJO implementation, i have done something similar to process exceptions in
asynchronous continuations. There i had to implement the scheme that you mention: in
case of exception, rollback the transaction, and then start a new to decrement the retry
counter. If it is 0, mark it so that it doesn't keep on executing.
But i didn't give any facility for automatically processing dead messages. But you
can see them in the newest console.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069594#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...