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

@BindToRegistry not working with @ApplicationScoped route builders #1505

Closed
aldettinger opened this issue Jul 30, 2020 · 2 comments
Closed

Comments

@aldettinger
Copy link
Contributor

This behaviour could be reproduced in camel-grok itests route by attempting to replace explicit bindToRegistry calls with @BindToRegistry.

The route can't start as @BindToRegistry Grok patterns are not present in the registry when GrokDataFormat.start() is called.
As far as I could tell, it seems to me that bean post processing never occurs in this scenario. So we may have even more annotations that are not working.

Would one agree it's an issue ? Would adding bean processing in this scenario be the solution ? where/when ?

@lburgazzoli
Copy link
Contributor

I think this is expected as back in the earlier days we decided that if you rely on CDi then you should use @produces as it is more idiomatic

@aldettinger
Copy link
Contributor Author

Thanks for sharing Luca, I was able to achieve this effect with qualified producer fields.

@ppalaga ppalaga added this to the No fix/wont't fix milestone Aug 10, 2020
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

No branches or pull requests

3 participants