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:
5932 OSGi Service Platform Core Companion Co
Hi Richard,
On 3/13/2012 11:58 AM, Richard S. Hall wrote:
However, I can talk about general OSGi policy: If your bundle is
expected to provide functionality to client bundles and client bundles
can reasonably expect to obtain (or witness or whatever) your provided
functionality without bei
Unfortunately much of this has to do with how the Eclipse platform is
managed and the policy used to activate bundles when provisioned within an
Eclipse platform installation. As a general rule, if your bundle does not
provide any OSGi services then it likely can use the lazy activation
policy. B
On 3/13/12 14:45 , Scott Lewis wrote:
Hi Richard,
On 3/13/2012 9:40 AM, Richard S. Hall wrote:
To be clear, this has nothing to do with running on other framework
impls, it is an artifact of using a lazy activation policy. If you
have a bundle that is lazy and other bundles are waiting for
Hi Richard,
On 3/13/2012 9:40 AM, Richard S. Hall wrote:
To be clear, this has nothing to do with running on other framework
impls, it is an artifact of using a lazy activation policy. If you
have a bundle that is lazy and other bundles are waiting for it to do
something in order to procee
On 3/13/12 10:49 , Scott Lewis wrote:
Hi,
ECF has consumers that use our OSGi remote services implementation in
client-server use cases. Some of these also use other framework
impls (e.g. felix) for the remote service host and/or consumer.
As a plugin to Eclipse, we use Bundle-ActivationPo
Hi,
ECF has consumers that use our OSGi remote services implementation in
client-server use cases. Some of these also use other framework impls
(e.g. felix) for the remote service host and/or consumer.
As a plugin to Eclipse, we use Bundle-ActivationPolicy: lazy for
many/most of our bundle
