-
Notifications
You must be signed in to change notification settings - Fork 52
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
CDI with Camel K runtime 1.7. #770
Comments
CDI in camel-k does not work at the moment, i.e. it is not possible to use @Inject on a camel-k integration. |
when do you plan to add there? |
We don't have any concrete ETA at the moment, we may have a look at this when working on camel-k 2.0 but again, no concrete ETA. If you have any spare time to look at implementing it, then it would be very appreciated |
Can you please refer me to target design, current state, documentation? I'll take a look at it. What actually solved #362? |
Any update? |
@ogomezdi the plan is to work on supporting directly Camel Quarkus out of the box, hence supporting CDI and any other Camel Quarkus feature. Maybe in Camel K 2.6 or 2.7 this should be already available. Keep it tuned. |
CDI does not work with Camel K runtime 1.7. The route is deployed, but when using the injected bean I get either a "nullpointerexception" or "bean not found". I tried it on an example from your project https://github.com/apache/camel-k/tree/aff450bfcccfa35ac0496336b1ea3801e4f8118f/e2e/yaks/openshift/monitoring/app
as well as on examples that work on Camel in combination with Quarkus (quarkus Di, spring DI). I enclose in the attachment.
I ask for verification / advice. It seems like #362 issue.
Thank you.
CDI_pokus.zip
The text was updated successfully, but these errors were encountered: