[
https://issues.apache.org/jira/browse/CAMEL-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164821#comment-14164821
]
ASF GitHub Bot commented on CAMEL-6380:
---------------------------------------
GitHub user aaronjwhiteside opened a pull request:
https://github.com/apache/camel/pull/297
Initial take on CAMEL-6380
Created a ModelJAXBContextFactory and replaced all usages of
JAXBContext.newInstance() with a call to the factory.
This would be the first step in a multistep change, wanted to get feedback
on what I have done so far..
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aaronjwhiteside/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/297.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #297
----
commit c72d335f066dd041b3abb57937f37fdc7e860357
Author: Aaron Whiteside <aaronjwhites...@gmail.com>
Date: 2014-10-09T06:12:40Z
Initial take on CAMEL-6380
Created a ModelJAXBContextFactory and replaced all usages of
JAXBContext.newInstance() with a call to the factory.
----
> 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)
