Hi,
Thanks a lot... for such a fast reply.
Ok I get the concpet.
You are correct I was trying to avoid the large overhead and the time
required of starting all
the bundle during the launch of the Framewrok..
So I guess now they all need to be started...
A small doubt what does the lazy atrribute
A lot of Eclipse bundles use Bundle-ActivationPolicy: lazy. That's
because they want to have Bundle-Activators *AND* have those bundles
be free to start (also known as having their cake and eating it!)
But frankly it's just for legacy reasons. If you're creating a new
bundle using DS, you don't
We do register the instance location as a Location service with type=osgi.instance.area service property. Are you saying you do not see this service registered at all in your environment?Tom-equinox-dev-boun...@eclipse.org wrote: -To: Equinox development mailing list
I have not looked at it myself, but I have been told that no service
registration even was ever being sent.
On 2011-02-18, at 11:49 AM, Thomas Watson wrote:
We do register the instance location as a Location service with
type=osgi.instance.area service property. Are you saying you do not
The only time a location service for the instance area should not be registered is if you set the configuration option osgi.instance.area=none. Otherwise we should be registering the location service and optionally setting it to a value specified by the configuration option osgi.instance.area or
equinox-dev,
IPZilla records show that one or more of the projects on which you are
developer are in need of attention. The following CQs have been in the
'awaiting_project' status for over 3 weeks and need your team to take
action.
rt.equinox:
4541 OSGi Service Platform Core Companion
