Chris,
FYI - I tried using the product def’n editor to set the bundles
start levels. I had a problem when using the “default” start level. It set
the entry in the config.ini to “@0”. This caused an error when starting the
server-side Eclipse environment. Once I changed these to a specific start
level (“@4”), everything did work.
BTW – I was surprised that bundles marked for started were defined
via “osgi.bundles”, instead of setting CU’s to update the bundle.info.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
From:
equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On
Behalf Of Chris Aniszczyk
Sent: Wednesday, April 15, 2009 4:03 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Autostarting Bundles
On Wed, Apr 15, 2009 at 2:51 PM, J B <moatas@xxxxxxxxx> wrote:
I have a small server-side equinox application running.
I would like
to autostart a couple of other bundles automatically. The
Eclipse-AutoStart is deprecated, and the Bundle-ActivationPolicy only
accepts 'lazy' as a value.
Is there an accepted way to auto start bundles without having the
explicitly in the config.ini?
We have used a solution in the past that require the plugins wishing
autostart to register an extension to a service that will start them
on their behalf. But it seems like there must be a different way.
So, is there a reason you need bundles autostarted? Is this something that
could be solved using Declarative Services (DS) since DS now listens for lazy
bundles?
One strategy outside the p2.inf suggestion that Denis mentioned is using a
product definition and tweaking the start levels from there.
Cheers,
--
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource
| http://twitter.com/caniszczyk
|
