camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Renault (JIRA)" <>
Subject [jira] Commented: (CAMEL-1456) support to create a default camel context in OSGi platefrom
Date Fri, 13 Mar 2009 08:23:39 GMT


Guillaume Renault commented on CAMEL-1456:

Thanks for the add. I'll check this as soon as i can, and then close the issue.

> support to create a default camel context in OSGi platefrom
> -----------------------------------------------------------
>                 Key: CAMEL-1456
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-osgi
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.0.0, 1.6.1
> I got a user request for creating a default camel context  without any spring application
context involved.
> " As you may remember, i did an integration in JOnAS 5.1.X application server (Ali Tokmen
did it for JOnAS 4). JOnAS 5.X works on an OSGi gateway. My goal is to provide a service that
could manage CamelContext. I use iPOJO to take care of the OSGi aspects, but that's just a
detail here. The issue i have with the SpringCamelContext is when we get the factory, we then
ask for a CamelContext (with the present factoryBean, we get a SpringCamelContext) but this
one needs an ApplicationContext. In my case, i don't have it. The way i use my service is
the following :
>    1. First i'm deploying on the gateway the camel bundles that i need
>    2. I then deploy my bundle that provides the CamelService on the OSGi GateWay
>    3. I deploy an other bundle that uses this service. This bundle asks for CamelContext,
set the routes it needs using the service, and so on ...
> I never use spring in my environment, that's why i need to get a DefaultCamelContext,
mainly because of the ApplicationContext that is needed."
> So we can support the user to do this by adding a CamelContextFactory in the camel-osgi

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message