[ 
https://issues.apache.org/jira/browse/CAMEL-27269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-27269 started by Claus Ibsen.
-------------------------------------------
> camel-core - add the application-x-unchanged data type, which leaves the 
> message as it is
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-27269
>                 URL: https://issues.apache.org/jira/browse/CAMEL-27269
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.24.0
>
>
> A Kamelet declares the body it takes and gives with {{spec.dataTypes}}, and 
> Camel runs the transformer of each default. Many Kamelets leave the body as 
> it is or do not read it: the filters, the header, EIP and Kafka-routing 
> actions, {{log-sink}} and {{log-action}}, and the AWS sinks that ignore the 
> body. No data type transformer does nothing today, so these Kamelets cannot 
> declare data types, and tooling such as the YAML body type validator knows 
> nothing about them.
> Add a core data type transformer {{application-x-unchanged}}: it leaves the 
> body, its type and the headers as they are, and sets no {{Content-Type}}. Its 
> {{@BodyTypes}} say {{transformerIn}} {{any}} and {{transformerOut}} 
> {{unchanged}}, which the validator already reads as "the body after the 
> Kamelet is the body before it". It is one of the default transformers, and is 
> documented with the Kamelets in the body types page.
> Part of the data types work for the Kamelet catalog (camel-kamelets#3117, 
> CAMEL-25928): it unblocks 25 Kamelets.
> _Claude Code on behalf of Claus Ibsen_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to