Grokbase › Groups › Camel › users › March 2010
FAQ
Hi,

I don't think it's currently possible to have a single camelContext
and use the <import> tag to pull in routing information into that
context.

The usecase is that we have a single application with many routes,
each route is specific to an entity and I would prefer to keep the
entity specific information in a separate context file and import it
into the main camelContext. This would allow soft-deployment of code
and then activation of a route via deploying an entity specific
context.

Is this something that may be possible in the future?

Thanks,
Kev

Search Discussions

  • Claus Ibsen at Mar 23, 2010 at 8:58 am ⇧
    Hi

    Yes its not possible.
    Yes there is a ticket in JIRA to add such a feature

    Java DSL allows you to use multiple route builders.

    On Tue, Mar 23, 2010 at 9:02 AM, Kevin Jackson wrote:
    Hi,

    I don't think it's currently possible to have a single camelContext
    and use the <import> tag to pull in routing information into that
    context.

    The usecase is that we have a single application with many routes,
    each route is specific to an entity and I would prefer to keep the
    entity specific information in a separate context file and import it
    into the main camelContext.  This would allow soft-deployment of code
    and then activation of a route via deploying an entity specific
    context.

    Is this something that may be possible in the future?

    Thanks,
    Kev


    --
    Claus Ibsen
    Apache Camel Committer

    Author of Camel in Action: http://www.manning.com/ibsen/
    Open Source Integration: http://fusesource.com
    Blog: http://davsclaus.blogspot.com/
    Twitter: http://twitter.com/davsclaus
  • Willem Jiang at Mar 24, 2010 at 1:25 am ⇧
    CamelContext tag supports to use the routeBuilder to load the Java DSL
    RouteBuilder.
    Maybe you can put the specific Routebuilder configure into a single
    spring configuration file, and import it into the Spring configuration
    with a single CamelContext.

    Willem

    Claus Ibsen wrote:
    Hi

    Yes its not possible.
    Yes there is a ticket in JIRA to add such a feature

    Java DSL allows you to use multiple route builders.

    On Tue, Mar 23, 2010 at 9:02 AM, Kevin Jackson wrote:
    Hi,

    I don't think it's currently possible to have a single camelContext
    and use the <import> tag to pull in routing information into that
    context.

    The usecase is that we have a single application with many routes,
    each route is specific to an entity and I would prefer to keep the
    entity specific information in a separate context file and import it
    into the main camelContext. This would allow soft-deployment of code
    and then activation of a route via deploying an entity specific
    context.

    Is this something that may be possible in the future?

    Thanks,
    Kev
  • Wayne Keenan at Mar 23, 2010 at 10:50 am ⇧
    Hi,

    You might want to look at springs classpath*: mechanism.

    I am using it to pull in in all the spring xml files that match a particular
    pattern fo my app; some spring files may have their own camelContext, so
    although you dont have a single camelContext you do get discrete config
    files. This may or may not fit your situation, e.g.:

    <!-- import al Spring config files -->
    <import resource="classpath*:*-camel-spring.xml"/>



    Regards
    Wayne
    On Tue, Mar 23, 2010 at 8:02 AM, Kevin Jackson wrote:

    Hi,

    I don't think it's currently possible to have a single camelContext
    and use the <import> tag to pull in routing information into that
    context.

    The usecase is that we have a single application with many routes,
    each route is specific to an entity and I would prefer to keep the
    entity specific information in a separate context file and import it
    into the main camelContext. This would allow soft-deployment of code
    and then activation of a route via deploying an entity specific
    context.

    Is this something that may be possible in the future?

    Thanks,
    Kev

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupusers @
categoriescamel
postedMar 23, '10 at 8:03a
activeMar 24, '10 at 1:25a
posts4
users4
websitecamel.apache.org

4 users in discussion

Claus Ibsen: 1 post Kevin Jackson: 1 post Willem Jiang: 1 post Wayne Keenan: 1 post

Content

People

Support

Translate

site design / logo © 2023 Grokbase