Docs:

• Camel Quarkus BEAN
• Camel 3 BEAN

Camel Quarkus ENG Component Planning Document

• document maps the progress of porting the Camel 3 components, dataformats, languages, EIP (TBD), others into Camel Quarkus runtime - JVM and Native mode

Definition of done:

• identify and fill the high-level features/use cases (even the ones it brings via transitive dependency on Camel 3 or Quarkus)
• identify transitive dependencies on quarkus extensions and make sure it is supported on upcoming Quarkus release
• identify if the use cases/features are present in quickstarts/camel-quarkus-examples
• identify the test coverage of the high-level features in integration-test or the quickstarts
• PM/ENG/QE agree on if everything of the features is supported in the product
• review if the tests contains test for each high level feature of the component

Feature/Use cases of the component/Support for TP1:

• Bean component, bean:beanName invoke a method on a bean instance looked up in the Camel registry - Supported
• Class component, class:beanName invoke a method on a class instance managed by the component - Unsupported - no tests in Camel Quarkus
• Bean method language - invoke a method on a bean instance looked up in the Camel registry - Unsupported - no tests in Camel Quarkus

QE TP1:

• for JVM and TP the testcoverage is sufficient

ENG TP1:

• ppalaga done with the support limitations mentioned above