-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(engine): Introduce operation log for sync message correlations #4014
Conversation
13d739c
to
c121942
Compare
if (variablesEnabled && execution != null) { | ||
|
||
ProcessInstance processInstance = execution.getProcessInstance(); | ||
resultWithVariables.setProcessInstance(processInstance); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hint for the reviewer: This line is not directly associated with the feature but it is necessary to set the process instance for the message correlation, otherwise the operation log will not contain the process instance. I believe this was not implemented by mistake.
066b4c0
to
b4382df
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Nice work! Left two suggestions.
engine/src/main/java/org/camunda/bpm/engine/impl/cfg/ProcessEngineConfigurationImpl.java
Outdated
Show resolved
Hide resolved
engine/src/main/java/org/camunda/bpm/engine/impl/history/SynchronousOperationLogProducer.java
Outdated
Show resolved
Hide resolved
engine/src/main/java/org/camunda/bpm/engine/impl/history/SynchronousOperationLogProducer.java
Outdated
Show resolved
Hide resolved
b4382df
to
5939769
Compare
Related to #3900