Skip to content

Conversation

artembilan
Copy link
Member

If a payload of the message in the flow is a org.reactivestreams.Publisher,
it must be subscribed somewhere downstream to initiate reactive processing.
The NullChannel just ignores the message altogether and therefore Publisher
is lost

  • Check the payload of the message in the NullChannel for Publisher type
    and subscribe to it
  • Verify in the test and mention this logic in the docs

Cherry-pick to 5.4.x

@artembilan
Copy link
Member Author

Here is a Gitter discussion on the matter: https://gitter.im/spring-projects/spring-integration?at=5fdb3542d75db604c1959651

If a payload of the message in the flow is a `org.reactivestreams.Publisher`,
it must be subscribed somewhere downstream to initiate reactive processing.
The `NullChannel` just ignores the message altogether and therefore `Publisher`
is lost

* Check the payload of the message in the `NullChannel` for `Publisher` type
and subscribe to it
* Verify in the test and mention this logic in the docs

**Cherry-pick to 5.4.x**
@artembilan artembilan force-pushed the NullChannel_&_Publisher branch from cc92412 to e051f0d Compare December 21, 2020 22:32
Co-authored-by: Gary Russell <grussell@vmware.com>
@garyrussell garyrussell merged commit c38da2f into spring-projects:master Dec 22, 2020
garyrussell added a commit that referenced this pull request Dec 22, 2020
* Subscribe to Publisher in the NullChannel

If a payload of the message in the flow is a `org.reactivestreams.Publisher`,
it must be subscribed somewhere downstream to initiate reactive processing.
The `NullChannel` just ignores the message altogether and therefore `Publisher`
is lost

* Check the payload of the message in the `NullChannel` for `Publisher` type
and subscribe to it
* Verify in the test and mention this logic in the docs

**Cherry-pick to 5.4.x**

* Apply suggestions from code review

Co-authored-by: Gary Russell <grussell@vmware.com>

Co-authored-by: Gary Russell <grussell@vmware.com>
@garyrussell
Copy link
Contributor

Cherry-picked as 5ed8c11

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