Re: [ecf-dev] NullpointerException in RemoteServiceAdmin

[Peter Hermsdorf <peter.hermsdorf@xxxxxxxxx>]

Hi,

Mat, thanks for your comments.

Am 08.10.2018 um 17:45 schrieb Mat Booth:

On Fri, 28 Sep 2018 at 17:42, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:

On 9/28/2018 4:03 AM, Peter Hermsdorf wrote:
>
> Hi Scott,
>
> thanks (again) for fixing the issue with the serialization. I finally
> could upgrade to ECF 3.14.1 with the additional bundles from the
> snapshot build with the 3 bug fixes. I haven't observed any additional
> issues - nor the test suite.
>
> Just one more thing: when building the product i stumbled across the
> following error:
>
> org.eclipse.ecf.remoteservice.feature.feature.group
> 2.5.0.v20180409-2248 depends on:
> org.eclipse.ecf.remoteservice.asyncproxy [2.1.0.v20180409-2248]
>
> Maybe it would be possible to define that dependency as optional as
> addition to bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=539469 .
>

I'm not sure.  I don't immediately know how we would have the feature
optionally include the 2.1 and 1.1 bundles.   One or the other are
required, based upon the dependencies as Peter points out.   Mat:  do
you know how to do that?

Hmm, I'm not sure you can. Eclipse "features" are kind of a hacky hold-over from the pre-OSGi days...

I think the easiest way to workaround this would be not to include the "o.e.ecf.remoteservice.feature" feature in one's product definition, but rather simply include the "o.e.ecf.remoteservice" bundle and the "o.e.ecf.remoteservice.asyncproxy" version of your choice instead.

My problem here was that i had a dependency to the bundle o.e.ecf.osgi.services.distribution which is in feature o.e.ecf.osgi.services.feature which has a dependency to o.e.ecf.remoteservice.feature which includes both versions of the asyncproxy bundles.

I tried removing the o.e.ecf.osgi.services.feature and adding a dependency to o.e.ecf.osgi.services.distribution and the asyncproxy bundle like this:

<import plugin="org.eclipse.ecf.remoteservice.asyncproxy" version="1.1.100" match="compatible"/>

and it does work for me. The correct version is included in the product.

I could live with that solution. It's not too hacky and can be easily removed when we update target platform and then can use asyncproxy bundle version 2.

Thanks for the hints!

Bye Peter