On Fri, Nov 16, 2012 at 1:17 PM, Donald Whytock wrote:
> Sorry, my project site was recently hacked. I'll have to find my
> archives. Ping me in a week if I haven't responded, please.
Okay...here's some hastily-thrown-together, untested code samples that
might nevertheless tell you what I mean.
On Fri, Nov 16, 2012 at 9:13 AM, ddewaele wrote:
> Donald Whytock wrote
>> The preferred way in OSGI is having a BundleListener listen for a
>> STARTED event. You'd put this in the bundles that are trying to
>> create routes.
>
> As soon as my bundle containing the camel route is started, the Spr
the line,
working with a non OSGI based Camel Context in an OSGI container will get us
into trouble.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-as-an-OSGI-bundle-OSGI-detection-strategy-tp5722787p5722864.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On Thu, Nov 15, 2012 at 11:53 AM, ddewaele wrote:
> Hi,
>
> I'm deploying Camel as an OSGI bundle (part of an EBA) on Websphere using
> the Spring OSGI extender.
> When the bundle is started, the camelContext is started and the route is up
> and running.
>
> I did notice however that it is not det
start-order dependency ?
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-as-an-OSGI-bundle-OSGI-detection-strategy-tp5722787.html
Sent from the Camel - Users mailing list archive at Nabble.com.
