You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2013/05/20 05:17:16 UTC
[jira] [Commented] (CAMEL-6380) Custom extensions to Camel's XML
configuration
[ https://issues.apache.org/jira/browse/CAMEL-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661744#comment-13661744 ]
Willem Jiang commented on CAMEL-6380:
-------------------------------------
Even Camel can load extensions jaxb context, I don't think it is easy to add the schema validation and customer parser in current Camel 2.x architecture.
Maybe we can consider it as new feature of Camel 3.0.
> Custom extensions to Camel's XML configuration
> ----------------------------------------------
>
> Key: CAMEL-6380
> URL: https://issues.apache.org/jira/browse/CAMEL-6380
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.11.0
> Reporter: Aaron Whiteside
>
> 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