[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Virgo and ECF remote services
- From: Hristo Iliev <hsiliev@xxxxxxxxx>
- Date: Wed, 29 Dec 2010 22:09:24 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=vaqfsC9Mllucy2LdOOUOfFS4UiGpywklrdSEWPkhBtBpl6ICTVtXpiKxpG5ES7w1yX s/GIpZZua94EuDuxeiVuMGztpPeqSVwDblfAJVx/R8F3B1JIMBr4+hzQWwNFmks5ZCO5 fD/8iZno/f7b7JYe6C2g3YsbhIE0GgSNJR4IQ=
Peter already found us  :) I'm not sure if he managed to deal with Virgo and equinox common - no answer from him, but if he or someone else needs assistance we are here (forums+mailing list).
Virgo does not include remoteserviceadmin in its kernel or web distributions, but I guess you can try running it on top and share the results. The topic sounds interesting.
On 29 December 2010 18:55, Scott Lewis <slewis@xxxxxxxxxxxxx>
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.
virgo-dev mailing list