Eclipse Community Forums: Equinox » Why my bundle is always in state resolved initially

Home » Eclipse Projects » Equinox » Why my bundle is always in state resolved initially

Why my bundle is always in state resolved initially [message #481267]

Thu, 20 August 2009 05:45

Eclipse User

Hi,

I have set up an environment how described in the equinox quick start
guide:

somedir/
configuration/
config.ini
org.eclipse.osgi_3.3.0.jar
org.eclipse.equinox.common_3.3.0.jar
org.eclipse.update.configurator_3.2.100.jar
plugins/
B1.jar
B2.jar

My problem is that the bundles in the folder plugins are always in the
state resolved after starting the osgi framework. I have to start them
manually. The lazy attribute in the manifest.mf is not set. So according
to the spec the bundles should go to the active state. Or I am wrong ?
There is no log file or exception.

Thanks
Oliver

Re: Why my bundle is always in state resolved initially [message #482225 is a reply to message #481267]

Tue, 25 August 2009 14:12

Eclipse User

Oliver Pfau wrote:
> My problem is that the bundles in the folder plugins are always in the
> state resolved after starting the osgi framework. I have to start them
> manually. The lazy attribute in the manifest.mf is not set. So according
> to the spec the bundles should go to the active state. Or I am wrong ?

I stumbled into this as well, and it turns out bundles are not
auto-started by default (and neither is there a way to specify that a
bundle should be auto-started in its manifest).

Some options:

- If you have a .product file, you can list the bundle there with
autoStart=true.

- Edit the platform's bundles.info file (last value indicates started or
not).

- Create a p2.inf file in the bundle's META-INF with the following
contents:

instructions.configure =
setStartLevel(startLevel:4);
markStarted(started: true);

Note that once a bundle is started (manually or otherwise), the platform
should remember the state across sessions.

Previous Topic:	Modifying @user.home location
Next Topic:	Question about custom HttpContext (Followup on Bug 287033)

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 02 11:02:55 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter