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

Inconsistency in auto-configuration between spring-cloud-function-web and stream #1678

Closed
olegz opened this issue Mar 29, 2019 · 2 comments
Closed
Assignees

Comments

@olegz
Copy link
Contributor

olegz commented Mar 29, 2019

See this stack overflow discussion for more details

@olegz olegz added this to the 2.2.x milestone Mar 29, 2019
@olegz olegz self-assigned this Mar 29, 2019
@olegz
Copy link
Contributor Author

olegz commented Mar 29, 2019

The issue is related to the lifecycle phase where ContextFunctionCatalogAutoConfiguration gathers functional beans. Currently it is InitializingBean and gathers all functions in afterPropertioesSet, hence initiating their creation. However, if such function bean takes argument (e.g. MessageChannel, Source etc) it is not yet created/available due to the EnableBinding driven logic.

@olegz olegz modified the milestones: 2.2.x, 2.3.x May 8, 2019
@olegz
Copy link
Contributor Author

olegz commented May 17, 2019

This has actually been resolved with 9044809

@olegz olegz closed this as completed May 17, 2019
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

2 participants