Skip to content

Identify a pulling Messaging Gateway method as an Outbound Channel Adapter EI pattern. #3120

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

Closed
artembilan opened this issue Dec 12, 2019 · 1 comment

Comments

@artembilan
Copy link
Member

See https://docs.spring.io/spring-integration/reference/html/messaging-endpoints.html#gateway-calling-no-argument-methods

When invoking methods on a Gateway interface that do not have any arguments, the default behavior is to receive a Message from a PollableChannel.

In this case a Messaging Gateway components is going to be present in the end of flow.

@artembilan artembilan modified the milestones: 5.3.x, 5.3.0.M1 Dec 12, 2019
artembilan added a commit to artembilan/spring-integration that referenced this issue Dec 12, 2019
Fixes spring-projects#3120

The messaging gateway method without arguments works as a
polling channel adapter.
In this case a Messaging Gateway component is present in the end of flow.
Therefore we treat it as an `outbound_channel_adapter`
garyrussell pushed a commit that referenced this issue Dec 12, 2019
Fixes #3120

The messaging gateway method without arguments works as a
polling channel adapter.
In this case a Messaging Gateway component is present in the end of flow.
Therefore we treat it as an `outbound_channel_adapter`
artembilan added a commit that referenced this issue Dec 12, 2019
Fixes #3120

The messaging gateway method without arguments works as a
polling channel adapter.
In this case a Messaging Gateway component is present in the end of flow.
Therefore we treat it as an `outbound_channel_adapter`
@artembilan
Copy link
Member Author

Fixed via: bc8e775

artembilan added a commit that referenced this issue Dec 26, 2019
Fixes #3120

The messaging gateway method without arguments works as a
polling channel adapter.
In this case a Messaging Gateway component is present in the end of flow.
Therefore we treat it as an `outbound_channel_adapter`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant