-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Idea to support execution listeners #27
Labels
Comments
I like this idea. We could add this behaviour to our converter as well as to the adapter. |
Scope: Only the migration tool will support this. |
@jangalinski tagging you here to match your PR from the hackday with the issue |
Thanks. I will do some cleaning up first |
see #280 |
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Assumption: listeners have to be "clean" as well, e.g. they should not invoke
execution.getProcessEngineServices()
.The transaction behavior is handled in the task worker as all methods are called in a given sequence and any exception is catched in the adapter.
The text was updated successfully, but these errors were encountered: