davsclaus commented on issue #3117: URL: https://github.com/apache/camel-kamelets/issues/3117#issuecomment-7035575511
**Two Camel bugs found while preparing batch 9** (verified with `camel run` on Camel main): - [CAMEL-27289](https://issues.apache.org/jira/browse/CAMEL-27289): the transformer registry can use the transformer of the previous step's data type instead of the Kamelet's own `in` type. This happens when the `in` transformer was not loaded yet. Only `binary` and `text` (and the new `application-x-unchanged`) load at startup, so `in` defaults of `json`, `struct`, `java-object`, `avro-binary` and `protobuf-binary` are affected. With the no-op type of CAMEL-27269 the problem would become common, so the pass-through defaults (batch 9a) wait for this fix. - [CAMEL-27290](https://issues.apache.org/jira/browse/CAMEL-27290): with the Kamelet EIP (`- kamelet: name: x-action`), an action's `out` default runs after the rest of the calling route. `to: kamelet:x-action` is not affected. This is the same kind of problem CAMEL-27258 fixed for sources. Both are targeted at 4.24.0. Batch 9b (`binary` on the object and file Kamelets) is not affected and is in progress. _Claude Code on behalf of Claus Ibsen_ -- 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]
