| OSGi does not reload previously installed bundles [message #66441] |
Fri, 12 May 2006 01:27  |
Eclipse User |
|
|
|
Originally posted by: kkiran7.gmail.com
I am using 3.11 release of Equinox and I have written
some sample bundles to test.
java -jar org.eclipse.osgi.jar -console and on the
console , I install a bundle file :/C:/path/somebundle.jar.
I exit the OSGi console and re-launch again. However, I
don't see the previously installed bundle when I query
on the console.
Actually, I was trying to do the same thing programmatically,
by extending the eclipse implementation of OSGi and using
BundleContext as a starting point for all the bundle installation/
querying etc. However, I noticed that after the framework is
launched, and I query BundleContex.getBundles(), I get only
"System Bundle", although I can see my bundle in the "configuration"
folder.
Sorry if I am missing something. The last time I checked the
API, it felt as if BundleContext is the king. Please help me.
|
|
|
| Re: OSGi does not reload previously installed bundles [message #66462 is a reply to message #66441] |
Fri, 12 May 2006 02:52  |
| Eclipse User |
|
|
|
Originally posted by: kkiran7.gmail.com
On Fri, 12 May 2006 14:27:26 +0900, Kiran Kuppa <kkiran7@gmail.com> wrote:
Oops! I could use EclipseStarter.shutdown() to shut cleanly.
And bundles can be seen on restart.
>
> I am using 3.11 release of Equinox and I have written
> some sample bundles to test.
>
> java -jar org.eclipse.osgi.jar -console and on the
> console , I install a bundle file :/C:/path/somebundle.jar.
>
> I exit the OSGi console and re-launch again. However, I
> don't see the previously installed bundle when I query
> on the console.
>
> Actually, I was trying to do the same thing programmatically,
> by extending the eclipse implementation of OSGi and using
> BundleContext as a starting point for all the bundle installation/
> querying etc. However, I noticed that after the framework is
> launched, and I query BundleContex.getBundles(), I get only
> "System Bundle", although I can see my bundle in the "configuration"
> folder.
>
> Sorry if I am missing something. The last time I checked the
> API, it felt as if BundleContext is the king. Please help me.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
|
| OSGi does not reload previously installed bundles [message #73865 is a reply to message #66462] |
Sun, 01 October 2006 08:53 |
| Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
I have the same problem. My installed bundles are not reloaded when I
restart OSGi within the console.
Does anybody know this problem ?
Kiran Kuppa schrieb:
> On Fri, 12 May 2006 14:27:26 +0900, Kiran Kuppa <kkiran7@gmail.com> wrote:
>
> Oops! I could use EclipseStarter.shutdown() to shut cleanly.
> And bundles can be seen on restart.
>
>>
>> I am using 3.11 release of Equinox and I have written
>> some sample bundles to test.
>>
>> java -jar org.eclipse.osgi.jar -console and on the
>> console , I install a bundle file :/C:/path/somebundle.jar.
>>
>> I exit the OSGi console and re-launch again. However, I
>> don't see the previously installed bundle when I query
>> on the console.
>>
>> Actually, I was trying to do the same thing programmatically,
>> by extending the eclipse implementation of OSGi and using
>> BundleContext as a starting point for all the bundle installation/
>> querying etc. However, I noticed that after the framework is
>> launched, and I query BundleContex.getBundles(), I get only
>> "System Bundle", although I can see my bundle in the "configuration"
>> folder.
>>
>> Sorry if I am missing something. The last time I checked the
>> API, it felt as if BundleContext is the king. Please help me.
>
>
>
>
|
|
|
|
|
| Re: OSGi does not reload previously installed bundles [message #75459 is a reply to message #75377] |
Tue, 24 October 2006 15:51 |
| Eclipse User |
|
|
|
Originally posted by: alex_blewitt.yahoo.com
The default start level goes up to 6 when starting. Any bundles with a start priority higher than that won't be started automatically. If you call bundle.start() to explicitly bring the bundle up, then next time around when you re-start the framework, the bundle will remain in the started state (since it's explicitly been started in a previous session).
If you want to bring a bundle up manually, but don't want it to be started next time around, you have to fudge it by performing a bundle lookup for a file that you know exists in the bundle (e.g. the activator class name).
Alex.
|
|
|
Powered by
FUDForum. Page generated in 0.03982 seconds
Home