Hello Maciej, thanks for your response.
I have jbpm core embed in my web application and I am interacting with human task service remotely. My problem is basicaly about transactionality, I use Hibernate to manage transactions into my web application but I can't control the task service transactions because it's the up to task service to take care of it. So my problem is that I am not controlling the global transacionality, and if one exception is thrown in one of the operations I make over my invoice object, I can't tell task service not to commit the task (and not to change task from 'Created' to 'Completed' for example)
So as you said to Thomas, I guess there are two options: keep using task service remotely with JMS and make it local. Is there any preferable option?
I don't have experience with JMS and I remember I couldn't made it work as a local service in the past, based on the documentation examples. I am using jBPM 5.2 and don't know if there is any significantly improving in 5.3 version that can help me. Should I try to upgrade?
I also took a quick look to exception handling but I don't know if this could help in this case. What do you think?
Thank you very much.