[
https://issues.apache.org/jira/browse/CAMEL-16628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507077#comment-17507077
]
Claus Ibsen commented on CAMEL-16628:
-------------------------------------
Take a look at how uri endpoints are doing it where we use Java OO inheritance.
So the commons headers can be in a base class.
But if that can't work then I dont mind duplicating as we should have this as
now - easy to setup - and if there is 1 camel component that is complex, then
so be it, and you just duplicate the headers.
atomix is also a "bad component" and would be deprecated in the future. Atomix
is a dying project - there was only 2 basic commits last year
https://github.com/atomix/atomix/commits/master
> camel-core - SPI annotations for message headers
> ------------------------------------------------
>
> Key: CAMEL-16628
> URL: https://issues.apache.org/jira/browse/CAMEL-16628
> Project: Camel
> Issue Type: New Feature
> Components: build system, camel-core
> Reporter: Claus Ibsen
> Assignee: Nicolas Filotto
> Priority: Major
> Fix For: 3.16.0
>
>
> Like we have for endpoint options with @UriParam, we should have a new SPI
> annotation to markup headers that consumer/producers support.
> This allows us to generate that information into the component json file for
> tooling support, and also to generate this in the website documentation.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
