ppalaga edited a comment on issue #2492: URL: https://github.com/apache/camel-quarkus/issues/2492#issuecomment-829244641
Missing tests (TBD within this issue): * Pass the method name via `CamelBeanMethodName` header * "the type of the body is used to find a matching method; an error is thrown if a single method cannot be chosen unambiguously." * Use Exchange as the parameter itself, but then the return type must be void * Return a CompletionStage implementation (e.g. a CompletableFuture) * Have multiple params, e.g. `doSomething(String body, Registry r, Exchange e)` * Parameter binding annotations https://camel.apache.org/manual/latest/parameter-binding-annotations.html * Parameter literals `.bean(OrderService.class, "doSomething(*, true)")` - not sure this would work without simple language * Param types to select the right overload `hello(String,String)` TBD elsewhere: * `@org.apache.camel.Consume` https://camel.apache.org/manual/latest/pojo-consuming.html - see https://github.com/apache/camel-quarkus/issues/2539 * `@EndpointInject` https://camel.apache.org/manual/latest/pojo-producing.html#POJOProducing-EndpointInject - see https://github.com/apache/camel-quarkus/issues/2539 * `@org.apache.camel.Produce` https://camel.apache.org/manual/latest/pojo-producing.html#POJOProducing-HidingtheCamelAPIsFromYourCodeUsingProduce - see https://github.com/apache/camel-quarkus/issues/2539 * "If the bean can be converted to a Processor using the Type Converter mechanism, then this is used to process the message. " I do not think we need to test this specific scenario. But we should test Type Converters in general https://github.com/apache/camel-quarkus/issues/2537 * `org.apache.camel.component.bean.BeanInvocation` - does not exist anymore in Camel source tree, see https://issues.apache.org/jira/browse/CAMEL-16562 Scenarios covered already: * `@Handler` https://github.com/apache/camel-quarkus/blob/main/integration-tests/bean/src/main/java/org/apache/camel/quarkus/component/bean/WithHandlerBean.java#L33 -- 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. For queries about this service, please contact Infrastructure at: [email protected]
