On 5/24/11 11:13 PM, jguion wrote:
Hello,
I am developing an OSGI bundle runs a Camel route. When I start my bundle
from the Apache Karaf console, I realized that it is calling
apache.camel.impl.osgi.Activator as its activator even though in the
Manifest file it says the activator is my Activator class that implements
org.osgi.framework.BundleActivator. I have tried to extend Camel's Activator
class but Karaf was still was starting Camel's class. The log file indicated
it was using Camel's Activator :
10:52:21,705 | DEBUG | l Console Thread | Activator |
apache.camel.impl.osgi.Activator 98 | 61 - org.apache.camel.camel-core -
2.7.1 | Bundle started: org.company.generic-camel-route
I don't know how your BundleActivator looks like.
Please don't extend the Camel core's Acitvator.
As the Camel osgi activator is a bundle tracker which means it monitors
the all the installed bundle states. I don't astonish to see the log.
Does anyone know why it behaves like this? If I put a Camel-Context.xml file
in the META-INF/spring directory it starts my route but I would like to be
able to run my own Activator class like you would in an OSGI bundle not
using Camel. I am using Camel version 2.7.1 and Karaf 2.2.0.
Thanks,
Jeff
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Activator-OSGI-tp4422370p4422370.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com
