[ https://issues.apache.org/jira/browse/CAMEL-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164825#comment-14164825 ]
Aaron Whiteside commented on CAMEL-6380: ---------------------------------------- Submitted pull request #297, initial step in the direction of allowing custom xml extensions.. > Custom extensions to Camel's XML configuration > ---------------------------------------------- > > Key: CAMEL-6380 > URL: https://issues.apache.org/jira/browse/CAMEL-6380 > Project: Camel > Issue Type: New Feature > Components: camel-core > Affects Versions: 2.11.0 > Reporter: Aaron Whiteside > Fix For: 3.0.0, Future > > > Allow custom elements to be defined and used in Camel's XML configuration. > The use case I have is that we have a fair number of Processor's that take > various options and we dynamically load and unload routes from external XML > files (not in any spring contexts). > Currently we do this by reimplementing Camel's loadRoutesDefinition() method, > and supplying additional packages when creating the JAXBContext. It would be > good is there were an officially supported mechanism to do this. > We place our custom *Definitions in separate namespaces. > I imagine it wouldn't be too hard to add support to Camel to look for a > specific META-INF/services file and add the additional packages contained > within to the JAXBContext, when it is created. > I guess this also means the structure of *Definition classes would need to be > documented to allow others to take advantage of them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)