[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [equinox-dev] Autostarting Bundles
- From: "O'Flynn, Dennis" <Dennis.OFlynn@xxxxxxxxxxxxx>
- Date: Wed, 15 Apr 2009 15:58:15 -0400
- Delivered-to: firstname.lastname@example.org
- Importance: normal
- Priority: normal
- Thread-index: Acm+A7DuEzGbgWikQQijPrG8M3KVkAAAFPBQ
- Thread-topic: [equinox-dev] Autostarting Bundles
For now, the config.ini is probably your best option.
In Eclipse 3.5 Galileo, you will be able to use P2 touchpoint advice
file (p2.inf) to indicated your bundle should be "markStarted" as well
as set its "startLevel".
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.
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of J B
Sent: Wednesday, April 15, 2009 3:52 PM
Subject: [equinox-dev] Autostarting Bundles
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.
equinox-dev mailing list