Hi Fang,

Thanks for your response. Here dynamic loading means that if there is any 
change in a bundle, we have to restart the felix container for the changes to 
come into effect, but in karaf we do not have to restart the container it 
reloads the bundle automatically.
Can you please provide some pointer for export|import OSGI service.


Regards,
Shadab

From: Freeman Fang [mailto:[email protected]]
Sent: Friday, August 02, 2013 4:26 PM
To: [email protected]
Subject: Re: Migrate from felix to apache karaf

Hi,

Please elaborate your "dynamic" here.

Anyway, business logic depend on bundle start sequence isn't good practice in 
OSGi container, you may need consider a refactor to avoid it.
Also, specify start level isn't that reliable if you really need bundle start 
sequence, export|import OSGi service between bundles is the way to guarantee 
"sequence" thing work
-------------
Freeman(Yue) Fang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋



On 2013-8-2, at 下午6:25, Mohammad Shadab Ali wrote:


Hi,

I am planning to migrate to apache karaf from felix for dynamic loading of osgi 
bundle. I tried to place the project related osgi bundles and jars in the 
deploy directory. I have a set bundles termed as core bundles, which needs to 
be loaded first then the other bundles.
I tried with features.xml for ordering the bundles but features is for static 
loading and not for dynamic loading
Is there a way in karaf to define the start-level for a bundle.

I am using apache-karaf-2.3.0 version.


Regards,
Shadab


________________________________
*** This e-mail (and any attachments), is confidential and may be privileged. 
It may be read, copied and used only
by intended recipients. Unauthorized access to this e-mail (or attachments) and 
disclosure or copying of its
contents or any action taken in reliance on it is unlawful. Unintended 
recipients must notify the sender immediately
by e-mail/phone & delete it from their system without making any copies or 
disclosing it to a third person.***

This e-mail (and any attachments), is confidential and may be privileged. It 
may be read, copied and used only

by intended recipients. Unauthorized access to this e-mail (or attachments) and 
disclosure or copying of its

contents or any action taken in reliance on it is unlawful. Unintended 
recipients must notify the sender immediately

by e-mail/phone & delete it from their system without making any copies or 
disclosing it to a third person.





________________________________
*** This e-mail (and any attachments), is confidential and may be privileged. 
It may be read, copied and used only
by intended recipients. Unauthorized access to this e-mail (or attachments) and 
disclosure or copying of its
contents or any action taken in reliance on it is unlawful. Unintended 
recipients must notify the sender immediately
by e-mail/phone & delete it from their system without making any copies or 
disclosing it to a third person.***

This e-mail (and any attachments), is confidential and may be privileged. It 
may be read, copied and used only
by intended recipients. Unauthorized access to this e-mail (or attachments) and 
disclosure or copying of its 
contents or any action taken in reliance on it is unlawful. Unintended 
recipients must notify the sender immediately 
by e-mail/phone & delete it from their system without making any copies or 
disclosing it to a third person.

Reply via email to