[
https://issues.apache.org/jira/browse/CAMEL-17796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506803#comment-17506803
]
Claus Ibsen commented on CAMEL-17796:
-------------------------------------
Yeah we can use the label rules we have for uri endpoints, that would be okay
and is enough
if the label has the word: consumer then it is a header that the consumer added
if the label has the word: producer then it is a header that the producer added
otherwise its for both
> camel-core - SPI annotations for message headers to include in/out direction
> ----------------------------------------------------------------------------
>
> Key: CAMEL-17796
> URL: https://issues.apache.org/jira/browse/CAMEL-17796
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 3.16.0
>
>
> Message headers can be used as input, output or both. (Maybe need a better
> term)
> Input means input to a producer.
> And output means output from a consumer.
> For example the FILE_NAME header is both input and output, as input its used
> to control what name to write the file as. And as output its the actual file
> name the consumer has read.
> The timer component only has output headers, eg the fired time and so on.
> It would be good to have a way to mark this in the annotation and also
> generate that information in the json file, so we know and have it available
> for tooling and the website documentation.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
