[
https://issues.apache.org/jira/browse/CAMEL-15560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276507#comment-17276507
]
Claus Ibsen commented on CAMEL-15560:
-------------------------------------
I am not (yet) keen on Extension as in this case its not an extension to
CamelContext etc.
And you dont know which extensions there would be, and you need to pass in the
class which then often means you need to know what class to import. And then
you need to go hunt which classes there are (and Camel has many).
ExtendedCamelContext has a nice API with all available advanced APis. And
CamelContext the "normal api". Though yet it can be cleaned up a little bit
more.
Also its not a normal use-case to load xml into model classes for end users. So
if that takes 4 lines of code that is fine.
> generic route loader
> --------------------
>
> Key: CAMEL-15560
> URL: https://issues.apache.org/jira/browse/CAMEL-15560
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-api, camel-core-engine
> Reporter: Luca Burgazzoli
> Assignee: Luca Burgazzoli
> Priority: Major
> Fix For: 3.9.0
>
>
> In camel-k we have a mechanism to load routes written in different languages,
> in camel instead we only support XML.
> We should move the generic loader to Camel from Camel K and leave the
> implementations where they fit better.
> I'm proposing to remove the following methods from the ExtendedCamelContext
> and replace them with a generic discovery mechanism similar to the one used
> for components & co to find the appropriate loader based on the file
> extension.
> {code:java}
> /**
> * Sets a custom {@link XMLRoutesDefinitionLoader} to be used.
> */
> void setXMLRoutesDefinitionLoader(XMLRoutesDefinitionLoader
> xmlRoutesDefinitionLoader);
> /**
> * Gets the {@link XMLRoutesDefinitionLoader} to be used.
> */
> XMLRoutesDefinitionLoader getXMLRoutesDefinitionLoader();
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
