Re: [ecf-dev] major r-osgi problem

[Bryan Hunt <bhunt@xxxxxxx>]

The problem appears related to using R-OSGi directly by using the "service.remote.registration" property.  I can get around this problem if I can get the ECF zookeeper code working.  I'll look into that.

I did run into a problem switching to ECF 3.2.  If I set service.exported.interfaces to a specific interface, that interface will not be made available remotely.  I must specify * and all interfaces will be exported remotely.  This may be a blocker for me.  I have services that implement multiple interfaces, and only one of the interfaces should be made available remotely.

Bryan


On May 13, 2010, at 12:47 PM, Bryan Hunt wrote:

> Markus,
> 
> My runtime is based on Eclipse / Equinox 3.5.2 and ECF 3.1.  I'm going to give Eclipse / Equinox 3.6 and ECF 3.2 a try to see if I can reproduce the problem.
> 
> Bryan
> 
> On May 13, 2010, at 12:06 PM, Markus Alexander Kuppe wrote:
> 
>> On 05/13/2010 06:03 PM, Bryan Hunt wrote:
>>> I've run into a problem with r-osgi where the proxy bundles it's generating are throwing exceptions when they are started. The problem appears to be that the proxy bundles are generated with a start level of 1 and when they start, they attempt to get the Remoting service which hasn't been registered yet because the main r-osgi bundle hasn't started and registered the Remoting service.  Any chance this is a known problem that was fixed in ECF sometime after version 3.1?
>> 
>> Hi Bryan,
>> 
>> I haven't seen this before. Can you narrow it down to a certain
>> environment (OSGi framework,...)?
>> 
>> Markus
>> _______________________________________________
>> ecf-dev mailing list
>> ecf-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/ecf-dev
> 
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev