Declarative Service might be the way to go. The equinox app I am deploying is really just a shell of a server with P2 functionality for now (hopefully). I want to then provision new bundles into this server and have them auto-started. I have no way of knowing in advance which bundles will be provisioned to the container.
On Wed, Apr 15, 2009 at 4:02 PM, Chris Aniszczyk <[email protected]> wrote: > On Wed, Apr 15, 2009 at 2:51 PM, J B <[email protected]> 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 > > _______________________________________________ > equinox-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
