New Scenario: RequestScope custom context was removed after javax.enterprise
event propagation
#996
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When firing an async CDI Event, the requestScope context from the emitter briefly exists for the observer and is then terminated. This commit is a reproducer of this scenario that happens on
Quarkus 2.13.0.Final
How to reproduce
mvn clean verify -Dit.test=HttpAdvancedIT#keepRequestScopeValuesAfterEventPropagation -Dquarkus.platform.version=2.13.0.Final -Dquarkus.platform.group-id=io.quarkus.platform
Please select the relevant options.
Checklist: