Skip to content
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

Increase granularity of ProcessInstanceVariableDataEvent when using persistence #3719

Closed
Tracked by #1505
fjtirado opened this issue Oct 11, 2024 · 0 comments · Fixed by #3720
Closed
Tracked by #1505

Increase granularity of ProcessInstanceVariableDataEvent when using persistence #3719

fjtirado opened this issue Oct 11, 2024 · 0 comments · Fixed by #3720
Assignees

Comments

@fjtirado
Copy link
Contributor

Description

When using persistence, the unmarshall Jsonnode object is not an instance of KogitoObjectListenerAware.
Therefore, variable value of the kogito event that is generated when the workflow model is changed is the whole model, which leads to bigger events

Implementation ideas

Unserialize the json node as instance of KogitoObjectListenerAware

@fjtirado fjtirado self-assigned this Oct 11, 2024
fjtirado added a commit to fjtirado/kogito-runtimes that referenced this issue Oct 11, 2024
fjtirado added a commit to fjtirado/kogito-runtimes that referenced this issue Oct 14, 2024
fjtirado added a commit to fjtirado/kogito-runtimes that referenced this issue Oct 14, 2024
rgdoliveira pushed a commit to rgdoliveira/kogito-runtimes that referenced this issue Oct 24, 2024
apache#3720)

* [Fix apache#3719] Unmarshall return ObjectNode that is event sensitive

* [Fix apache#3719] Fixing IT test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant