davsclaus opened a new pull request, #28451: URL: https://github.com/apache/camel/pull/28451
## What [CAMEL-25928](https://issues.apache.org/jira/browse/CAMEL-25928): runtime checks of the catalog body types of the EIPs that other modules implement. The checks follow `EipBodyTypesTest` in camel-core, which covers the EIPs of core. The body types themselves are declared on the model classes in camel-core-model. Tests only, no declaration changed: the runtime matches each one. | Module | Test | What it shows | |---|---|---| | camel-resilience4j | `CircuitBreakerBodyTypesTest` (4 tests) | The steps of circuitBreaker start with the same body instance, and the body after is what they end with. When a step fails, or the circuit is forced open, onFallback starts with the original body, not the one the failed step set, and the body after is what onFallback ends with. | | camel-microprofile-fault-tolerance | `FaultToleranceBodyTypesTest` (4 tests) | The same, with the circuit opened by failing calls. | | camel-a2a | `A2ASubTaskBodyTypesTest` | The steps of a2aSubTask start with the same body. The body after is what they end with, or the same instance when they keep it. | | camel-kamelet | `KameletBodyTypesTest` | The body after a kamelet step is what the Kamelet's route leaves: a String, the same instance, or a List from three local Kamelets. That is the `unknown` of its eipOut. | | camel-langchain4j-tokenizer | `TokenizerBodyTypesTest` (3 tests) | Text gives a `String[]` body, the declared javaType. A byte[] is read as text. Any other object is read with `toString()`. | Found on the way, not fixed here: the tokenizer never ends an exchange with a null body, which waits forever. `TokenizerProcessor.process` does not catch what the tokenizer throws, here a NullPointerException, so the callback is never called. _Claude Code on behalf of davsclaus_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
