mkhudyakov commented on issue #1205:
URL:
https://github.com/apache/camel-kamelets/issues/1205#issuecomment-1351677377
Thank you a lot, @davsclaus, the injector helped
```
CamelContext camelContext = main.getCamelContext();
if (camelContext != null) {
Object clazzInstance =
main.getCamelContext().getRegistry().findSingleByType(clazz);
if (clazzInstance != null) {
System.out.println(clazz.getCanonicalName() + " already
registered");
return;
}
Injector injector = camelContext.getInjector();
main.configure().addConfiguration((CamelConfiguration)
injector.newInstance(clazz));
} else {
System.err.println("CamelContext is not defined");
}
```
Could you also clarify, is such approach, when dependency is defined through
the Kamelet, actually the way how it has to work once deployed to `K8S` /
`Camel K` ?
Or are the fat jars can be deployed to Camel K?
My goal with `KameletMain` is a transition from `Spring Boot with Camel` and
`camel route resource` being deployed to `K8S`.
Is there any 'executive summary' documentation, which explain the benefits
of Camel K as opposed to Spring Boot + Camel?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
