[
https://issues.apache.org/jira/browse/CAMEL-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670019#comment-13670019
]
Aaron Whiteside commented on CAMEL-6380:
----------------------------------------
Do you mean Camel currently supports loading XML routing definition extensions,
if so how?
Can you point me in the direction of the schema validation? I cannot find it or
any custom parser? Looks like pure JAXB to me..
I looked at \CamelNamespaceHandler, ModelHelper and
DefaultCamelContext.loadRoutesDefinition()..
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
