[ https://issues.apache.org/activemq/browse/CAMEL-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50493#action_50493 ]
Claus Ibsen commented on CAMEL-1455: ------------------------------------ James I have been thinking about adding some kind of MetaModel class that contains meta data about a given component/language/type converter/data format and what else we have in Camel. for starters it could be a repository you query with the given name MetaDataModel model = MetaDataRepository.getMetaDataForLanguage("xpath"); It could of course also just be a Map with keys for the meta data. Then its more flexible. Then we could contain - link to official documentation in our wiki - description - relates to - since, eg requires Camel 2.1 - artifact id, which .jar it comes from - and what else I do think at the same time we should consider if we can change how components, languages, data formats, type converters are loading on the fly in Camel today. I would like it to be component based, so there is a META-INF/service/camel/plugin file that has a complete list of what this current .jar contains - 0..n components - 0..n data formats - 0..n type converters - 0..n languages And if the .jar can not be loaded succesfully eg because of missing 3rd part .jars then we can report that as well. To avoid this problem with the type converters going crazy! Then also at assembly time we will be able to scan all .jars for ths plugin file and generate a master list that we can provide in camel-core so when someone asks for a component with scheme: pop3 then it will be able to report that you need: camel-main.jar in the classpath. Maybe we need a discussion on the dev forum? > camel-web now can link to components and languages on the camel website; > however we need to double check that the wiki pages match the IDs of the > component/language > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CAMEL-1455 > URL: https://issues.apache.org/activemq/browse/CAMEL-1455 > Project: Apache Camel > Issue Type: Improvement > Reporter: James Strachan > Fix For: 2.0.0 > > > I spotted that spring-events doesn't match for starters. > When we find we need to change the name of the wiki page to match the > component/language ID we could create dummy wiki pages which just {include} > the real pages using the confluence include macro - or rename the wiki page > and we could create symlink / redirects to the new page? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.