[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] How to consume HelloWorld remote OSGI Samples in eclipse platform
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Sat, 23 Apr 2011 09:55:03 -0700
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
On 4/22/2011 11:58 PM, Pradeep Fernando wrote:
So...Pradeep or Harshana and/or others...would you please describe the
conditions (in terms of the framework, the way the framework is started,
what bundle state things are in, etc), that lead to being able to reproduce
the bundle state exception that Pradeep reported? It would be much
appreciated...and hopefully by doing this we can completely avoid this issue
in the future.
In the case of hello world example that make use of activators/service
trackers instead of declarative services, I got that bundle state
exception issue., when i did "start
According to Markus's response then I tried to start the interface
bundle "hello.bundle". But it didnt work. Then with the help from this
forum discussion,  I figured out that we should get other bundles
in to "Active state" prior starting the
In the second run, I made sure other bundles were in Active state
before starting the
org.eclipse.ecf.remoteservices.hello.consumer.edef bundle. bundle.
However since OSGI runtime remembers the last state of bundles, in the
second run, rest of bundles including interface bundle were in Active
state AFA I can remember.
Thanks for describing what you did.
I assume that you are using Eclipse/Equinox 3.6.X...as I don't see this
with Equinox 3.7.
I now believe that this boils down to some issue with Equinox 3.6.X
classloading...having to do with the way the classloading is handled
with ServiceFactories (which ECF RSA uses for proxy creation). I
suspect that it relates to this classloading issue discussed on osgi-dev
In any event, a reasonable work around is to have the product config
autostart the org.eclipse.ecf.examples.remoteservices.hello bundle.
I've opened a bug to do this , and made the change to the product
Service Consumer (edef,generic).product ). This should fix things on
Equinox 3.6.x...as the new product config, when run will autostart the
o.e.e.e.remoteservices.hello bundle, prior to triggering the edef discovery.
Pradeep and/or others...I would appreciate some testing of the new
product config on 3.6.X Equinox...to verify that it does what's
necessary for things to operate seemlessly on 3.6.X. If you can, please
test on 3.6.2 and report results on the bug . Thanksinadvance for
Framework : Equinox
Target environment : Helios + ECF remote services target components.
run using given .product files.
Please let me know if i can give even a small help in this regard.
Happy to contribute.
(I would suggest putting in a new page with a link on the above page...to
give detailed information about bundle autostart/start levels, use of Felix,
Thanks and Regards,
Is this something specific to Felix?
ecf-dev mailing list
ecf-dev mailing list