Skip to content
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

INT-3668: Add late-binding for GatewayProxyFB #1418

Closed
wants to merge 1 commit into from

Conversation

artembilan
Copy link
Member

JIRA: https://jira.spring.io/browse/INT-3668

Note: the defaultRequestChannel, defaultReplyChannel and errorChannel remain as MessageChannel references,
since they are really some global shared and it looks logical to require those channels be populated by end-user directly

Cherry-pick to 4.1.x

JIRA: https://jira.spring.io/browse/INT-3668

Note: the `defaultRequestChannel`, `defaultReplyChannel` and `errorChannel` remain as `MessageChannel` references,
since they are really some global shared and it looks logical to require those channels be populated by end-user directly

**Cherry-pick to 4.1.x**
@artembilan
Copy link
Member Author

Additional change: removed start() call from the afterPropertiesSet() because this operation really should be postponed to the appropriate applicationContext initialization phase.

@@ -311,7 +311,6 @@ public String call() throws Exception {
this.asyncSubmitListenableType = submitType.getClass();
}
}
this.start();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although this is wrong, I don't think we can make this change on the backport - it could break usage outside of a Spring application context.

@garyrussell
Copy link
Contributor

Merged and cherry-picked.

@garyrussell garyrussell closed this Apr 2, 2015
@artembilan artembilan deleted the INT-3668 branch May 8, 2015 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants