davsclaus commented on pull request #7190: URL: https://github.com/apache/camel/pull/7190#issuecomment-1066042129
@essobedo oh my word is not a rule in law - you are the one that are actual implementing this and find out on the way what is a better solution. Unfortunately the Camel components was very _open ended_ when Camel was created/designed and this leads to where we are today with endpoint headers that are not well documented, defined consistently in a class named XXX or defined directly on the endpoint class, etc. But we have the power in our hands where we can implement what you work on, and then "fix" all the components in Apache Camel. We have done this over the years with adding documentation for every endpoint options etc. In the camel-catalog that prints a summary we can write a report which lists all the components that does not yet have headers marked up with @Metadata - then we can see how many we need to fix. This is what we did in the past. And some components will not have headers, and if so, then should we still have a header class, but keep it empty? About number of header classes, then that should be 1 class. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
