Signpost png from pngtree.com/ During the last weeks we’ve been asked questions around the direction we’re willing to take on the future development of Camel K. I think it would be good to have some blog in order to let the community understand where our efforts are going. It will be useful for every Camel K user and Camel K developer, as a guide for the future development of the project.
For Camel 3.16.0 we are removing the deprecated container-based test modules and replacing them with a new set of modules called Camel test-infra. They continue to support container-based tests via TestContainers, however they abstract the underlying test infrastructure. One of the great benefits for our project is that they allow us to more easily switch from container-based tests, to external instances. Previously, we would need to create a new test or implement a more complex design if we wanted to test both a container instance and an external service instance (i.
Beans and dependencies New Karavan preview release comes with Beans and dependencies configuration. Get it as a Standalone application or install VS Code extension from the Marketplace. Bean Configuration New Beans tab to configure Beans: Dependencies Configuration Configure Dependencies to access Beans outside Camel: DSL Bean mapping How to map Bean to DSL: just select from the list. Component Bean mapping How to map Bean to Component: just select from the list.