Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of foamdino@gmail.com designates
 72.14.220.155 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=UYCUkGQtuTrYFmseE7V6KskaX/YZY4IZcem3/y43BH7nw28nm/T+aNABuaXazYX0mf
         P9kBOUtXaiQ6u6YPgqAC+/aNnty1A/EclWZJL0Q6YbB3LXXate5imGJh6NIJTp1AEeK0
         o0QeMmXANWYW4vx/qYDPW7dBsZZ3C8798Ct+c=
MIME-Version: 1.0
Date: Tue, 23 Mar 2010 08:02:42 +0000
Message-ID: <ab8e556c1003230102o22c73050kfb30ea4537c19274@mail.gmail.com>
Subject: Importing routes into camel (spring) context
From: Kevin Jackson <foamdino@gmail.com>
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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