[
https://issues.apache.org/jira/browse/CAMEL-14066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated CAMEL-14066:
------------------------------------
Description:
In order to better separate all xml loading / parsing from the runtime, and in
preparation of CAMEL-14053, it would be interesting to remove the two methods
that accept an input stream and use JAXB underneath to load routes / rests
definitions.
>From a user point-of-view, the work around is quite simple and it's just a
>matter of calling
{{context.getExtension(Model.class).addRoutesDefinitions(ModelHelper.loadRoutesDefinition(context,
inputStream).getRoutes());}}
was:
In order to better separate all xml loading / parsing from the runtime, and in
preparation of CAMEL-14053, it would be interesting to remove the two methods
that accept an input stream and use JAXB underneath to load routes / rests
definitions.
>From a user point-of-view, the work around is quite simple and it's just a
>matter of calling
```
context.addRoutesDefinitions(ModelHelper.loadRoutesDefinition(context,
inputStream).getRoutes());
```
> Split route parsing from the main CamelContext api
> --------------------------------------------------
>
> Key: CAMEL-14066
> URL: https://issues.apache.org/jira/browse/CAMEL-14066
> Project: Camel
> Issue Type: Improvement
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 3.0.0.RC3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In order to better separate all xml loading / parsing from the runtime, and
> in preparation of CAMEL-14053, it would be interesting to remove the two
> methods that accept an input stream and use JAXB underneath to load routes /
> rests definitions.
> From a user point-of-view, the work around is quite simple and it's just a
> matter of calling
> {{context.getExtension(Model.class).addRoutesDefinitions(ModelHelper.loadRoutesDefinition(context,
> inputStream).getRoutes());}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
