Skip to content

Conversation

artembilan
Copy link
Member

When we do something like Flux.from(Publisher)
and don't compose it with the one involved in the Subscriber context, we lose this context.

  • Provide a mechanism to propagate a Reactor context over message header produce within that context.
  • Restore this context in the FluxMessageChannel for a new publisher we use in this channel

Cherry-pick to 6.0.x

When we do something like `Flux.from(Publisher)`
and don't compose it with the one involved in the `Subscriber` context,
we lose this context.

* Provide a mechanism to propagate a Reactor context over message header
produce within that context.
* Restore this context in the `FluxMessageChannel` for a new publisher
we use in this channel

**Cherry-pick to `6.0.x`**
Co-authored-by: Gary Russell <[email protected]>
@artembilan artembilan requested a review from garyrussell April 10, 2023 15:52
@garyrussell garyrussell merged commit 4f5250b into spring-projects:main Apr 10, 2023
garyrussell added a commit that referenced this pull request Apr 10, 2023
* Propagate Reactor context over headers

When we do something like `Flux.from(Publisher)`
and don't compose it with the one involved in the `Subscriber` context,
we lose this context.

* Provide a mechanism to propagate a Reactor context over message header
produce within that context.
* Restore this context in the `FluxMessageChannel` for a new publisher
we use in this channel

**Cherry-pick to `6.0.x`**

* Fix language in docs

Co-authored-by: Gary Russell <[email protected]>

---------

Co-authored-by: Gary Russell <[email protected]>
@garyrussell
Copy link
Contributor

...and cherry-picked to 6.0.x 863795c

@artembilan artembilan deleted the propagate_reactor_context_over_headers branch April 10, 2023 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants