You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/10/15 06:41:00 UTC

[jira] [Work logged] (CAMEL-14066) Split route parsing from the main CamelContext api

     [ https://issues.apache.org/jira/browse/CAMEL-14066?focusedWorklogId=328358&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-328358 ]

ASF GitHub Bot logged work on CAMEL-14066:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Oct/19 06:40
            Start Date: 15/Oct/19 06:40
    Worklog Time Spent: 10m 
      Work Description: gnodet commented on pull request #3246: [CAMEL-14066] Split route parsing from the main CamelContext api
URL: https://github.com/apache/camel/pull/3246
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 328358)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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.addRoutesDefinitions(ModelHelper.loadRoutesDefinition(context, inputStream).getRoutes());
> ```



--
This message was sent by Atlassian Jira
(v8.3.4#803005)