On 12/28/2010 10:21 PM, Hristo Iliev wrote:
Virgo has no problems resolving or deploying the equinox.common
bundle. These operations are working as expected.
As you perhaps already saw  the bundle has lazy activation
policy which causes confusion since its status is reported as
LAZY. This status appears to be (thanks to Glyn for the
explanation) a subset of STARTING. According to the specification
this is the expected behavior until the bundle is activated by
The issue for which I created bug 333174
is that removal of the equinox.common bundle triggers a stop,
which fails (as expected) if the bundle did not reach STARTED.
There is no real problem here since the removal is ok as well.
So in short - no tricks should be needed to have equinox.common
(or ECF) running with Virgo. Of course if you have some questions
or issues running ECF in Virgo please come back to us - we'll be
glad to help :)
I guess I still don't understand (since I haven't experienced it
myself), why folks like Peter  are having trouble with getting
ECF+equinox common running on Virgo. Do you think it's likely some
consequence of 333147? Should I direct Peter and other folks over
to this mailing list for assistance on these issues?
BTW...I'm finishing up the ECF impl of the OSGi Remote Service Admin
spec and am keen on using it on Virgo also. Does Virgo currently
distribute the OSGi remote service admin classes? (i.e.
On 29 December 2010 01:22, Scott Lewis <slewis@xxxxxxxxxxxxx>
I work on the ECF project . We have an implementation of
OSGi 4.2 remote services , and we're now finishing up an
implementation of the OSGi 4.2 remote services admin spec 
for release in late Feb 2011.
Recently, we've had several folks in our consumer community
(e.g. ) that have asked about using ECF remote services
along with Virgo. As far as I/we can tell, this should be
eminently doable, as Neil Bartlett has successfully run ECF
remote services (along with dependencies) on Felix .
However, some reports from users (e.g. ) have been that the
Virgo runtime does not resolve the org.eclipse.equinox.common
bundle. We have some dependencies on classes that are exposed
by equinox.common (as well as some other equinox APIs...like
jobs API...and concurrent API...and extension registry), but
these can/should/do run just fine inside of other OSGi
Is there some 'trick' to running equinox.common and some other
equinox pieces in Virgo that we can notify our/your users
about? It would be quite nice for both our user communities
if the ECF remote services and remote services admin were to
run easily inside of Virgo...and it seems to me this should be
doable. But perhaps I'm missing something.
Thanksinadvance for any information.
virgo-dev mailing list
virgo-dev mailing list