Type of change
Does this introduce a change in the core logic?
Does this introduce a change in the cloud provider implementation, if so which cloud?
Does this introduce a breaking change?
What is the current behavior?
Storage after migration to OQM service is not able to process
legal_changed events due to request scope boundaries in common code, because OQM is designed to use only pull subscribers.
What is the new/expected behavior?
Storage service context was split into two separate contexts, one for serving HTTP requests via API that is still bound to request scope, and one for message event processing which contains overridden bean definitions, not limited with request scope.
Have you added/updated Unit Tests and Integration Tests?