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 <[email protected]> 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
>
