[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Autostarting Bundles
- From: J B <moatas@xxxxxxxxx>
- Date: Fri, 17 Apr 2009 10:49:18 -0400
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=MBVaU56lZXpcuam4y9UUrPWd1oEmH/nmIVdKmfqP2W5cDRz2go8Z6djUkdkZ5SeirY OXqeskxnxg94+DzULNGhaM9Ec8mqkVWT8n0BttywmU+1DulAmSaaeZtVINJ9FoE5oBTQ L0Pv6mzHuawKVS7pAFRZydmvazLxJMrQiIHyE=
It is a headless eclipse environment. The idea is to 'forward deploy'
a small footprint container to many machines, with only enough
functionality to allow other bundles to be provisioned in and out of
it at a later date.
Right now, I am trying to just put together the most minimal osgi
application possible with the P2 bundles loaded. I then want to be
able to use the P2 console to provision a bundle from a remote
I was able to get the P2 console started, but haven't been able to
figure out how to provision a bundle using yet. Anyone have
experience with doing that?
On Thu, Apr 16, 2009 at 11:40 AM, O'Flynn, Dennis
> Timing is everything – thx for the fix. I’ll try it w/ the next I-Build.
> Re: including simpleconfigurator
> · I do include it. My product def’n is based upon feature
> configurations. I have a primary feature, that includes secondary
> features. The simpleconfigurator bundle is included in one of the secondary
> Re: server-side applications…
> · Are you using “org.osgi.service.application” as your server-side
> application model?
> · Running a headless eclipse runtime with set of plug-ins bound via
> extension points and/or OSGi service components?
> · Both?
> 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: Thursday, April 16, 2009 10:58 AM
> To: Equinox development mailing list
> Subject: Re: [equinox-dev] Autostarting Bundles
> On Thu, Apr 16, 2009 at 8:35 AM, O'Flynn, Dennis
> <Dennis.OFlynn@xxxxxxxxxxxxx> wrote:
> 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.
> You're on the bleeding edge a bit Dennis. I fixed that issue yesterday:
> 272361: don't write out 0 for start levels
> If you don't included simpleconfigurator in your product, everything will be
> on the osgi.bundles property. If you include simpleconfigurator, PDE should
> use it.
> Let me know if we can help, we have had great success using product
> definitions to manage server side applications.
> Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
> http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
> equinox-dev mailing list