Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » How Can a Bundle Start w/o the Calling Start Method
How Can a Bundle Start w/o the Calling Start Method [message #121481] Mon, 24 November 2008 18:49 Go to next message
Geoffry Roberts is currently offline Geoffry RobertsFriend
Messages: 71
Registered: July 2009
Member
All,

I have a bundle that seems to start well enough from the osgi command line
using the start command. I say seems to because the ss command says it is
started. In fact, I can start it and stop it at will with no errors
thrown. However, any attempt to get a reference to it always returns
null. I've set break points, I've placed System.out.printlns() in the
start and stop methods. But there is no break at the break points and no
output from my sysouts when I run the start/stop commands. It's as if
these methods are not being called at all. Yet, after a start command the
bundle shows as active; after the stop command it shows as resolved with
nary an error in sight.

I am doing all this in my eclipse ide. I once had a similar experience
when deploying to a stand alone equinox container. In that case, the
problem was solved by cleaning out what appeared to be some kind of cache
down in the configuration directory.

Could I have a dirty cache problem? If so how? I test bundles from the
ide all the time and have never encountered anything like this before.
Re: How Can a Bundle Start w/o the Calling Start Method [message #121490 is a reply to message #121481] Tue, 25 November 2008 07:12 Go to previous message
Danail Nachev is currently offline Danail NachevFriend
Messages: 110
Registered: July 2009
Senior Member
It seems like Equinox hasn't noticed your activator in the bundle
manifest. Change the configuration folder, wipe it out clean or just
tell launcher to clean it up for you. If you are still experiencing the
problem, try to reproduce the problem with minimal workspace and submit
a bug, if you succeed.

Geoffry Roberts wrote:
> All,
>
> I have a bundle that seems to start well enough from the osgi command
> line using the start command. I say seems to because the ss command
> says it is started. In fact, I can start it and stop it at will with no
> errors thrown. However, any attempt to get a reference to it always
> returns null. I've set break points, I've placed System.out.printlns()
> in the start and stop methods. But there is no break at the break points
> and no output from my sysouts when I run the start/stop commands. It's
> as if these methods are not being called at all. Yet, after a start
> command the bundle shows as active; after the stop command it shows as
> resolved with nary an error in sight.
>
> I am doing all this in my eclipse ide. I once had a similar experience
> when deploying to a stand alone equinox container. In that case, the
> problem was solved by cleaning out what appeared to be some kind of
> cache down in the configuration directory.
>
> Could I have a dirty cache problem? If so how? I test bundles from the
> ide all the time and have never encountered anything like this before.
>
Previous Topic:Difference between an OSGi bundle as jar/directory
Next Topic:Generating pack200 and compressed artifact/content list
Goto Forum:
  


Current Time: Tue Mar 19 02:09:22 GMT 2024

Powered by FUDForum. Page generated in 0.04198 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top