I have a sample DS component which exports a service. I want to use the ECF generic provider and JAX-RS provider at the same time.

I am registering it in the properties file as follows:
service.exported.configs=ecf.generic.server,\
ecf.jaxrs.jersey.server
ecf.generic.server.hostname=localhost
ecf.generic.server.port=4445
ecf.jaxrs.jersey.server.uri=http://localhost:8181/jersey

The endpoints aren't getting registered when used in this way. However, if I use any one of them independently, it works fine.

As per this page, multiple providers are supported.
https://wiki.eclipse.org/EIG:OSGi_Remote_Services

Any clue why it is not working for me?

Hi Scott,

Isn't the build automatically triggered and uploaded to [1]?

[1] http://download.eclipse.org/rt/ecf/snapshot/

Cheers,

Wim

That's simply amazing the time you spent writing this detailed post. Thanks a ton Scott! It's good that you could identify the problem and fix it.

I tried registering my own IHostContainerSelector service. I couldn't quite get it working yet. I see that my service is getting registered, I am not sure if it is somehow too late.
Can it be that the RemoteServiceAdmin constructor is kicking in getting the "defaultHostContainerSelector" you are creating there? I will have a deeper look later today (tonight here in Germany;)).

ECF looks pretty interesting and I don't know how I missed it until now. We have a huge eclipse development setup with several 1000 plugins. I am trying to define a new architecture for our tooling on how we can go from the local IDE concept to a distributed architecture where we reuse the OSGi components from distributed IDEs (using DOSGi) and from cloud (using REST) at the same time. The goal is to have only cloud solutions in the end, but ECF looks like a good transition path for us to have "hybrid" solutions rather than going for a big-bang.

This seems to me to allow you to not only gradually transition a non-distributed system to a distributed system, but also to choose, evaluate and update transports based upon things like performance, bandwidth, and/or security constraints, without having to rewrite service implementers or consumers. The value of separation of API from impl can be very useful (I assert) to achieve separation (not transparency!) between distribution contract (rpc) and distribution impl (rest+json, tcp+protobuf, mqtt, websockets, etc).

Cool! It worked when I used the Snapshot version. Thanks a lot.

I have Apache Karaf as the container and since there was no Karaf feature in the snapshot build, I manually downloaded the org.eclipse.ecf.osgi.services.remoteserviceadmin_4.5.200.xxx jar and installed it into Karaf with a "bundle:install file:". Not so elegant. Do you have a alternate suggestion on how to get it into Karaf before the maintenance build is available?

After using the Snapshot version and deploying my services into Karaf, I could use the REST services. However an eclipse plugin which consumes the remote OSGi services couldn't get it (although I can see the generic and jersey endpoints in the ECF view) . Perhaps the org.eclipse.ecf.osgi.services.remoteserviceadmin plugin in my Eclipse is still outdated. Does the client also use the org.eclipse.ecf.osgi.services.remoteserviceadmin plugin to communicate to a remote service?

!MESSAGE org.eclipse.core.runtime.Status[plugin=org.eclipse.ecf.osgi.services.remoteserviceadmin;code=4;message=org.eclipse.ecf.osgi.services.remoteserviceadmin.RemoteServiceAdmin:importService:No remote service container selected for endpoint=ECFEndpointDescription[{ecf.endpoint.id=http://localhost:8181/jersey, ecf.endpoint.id.ns=ecf.namespace.jaxrs, ecf.endpoint.ts=1501620321763, ecf.generic.server.hostname=localhost, ecf.generic.server.port=4445, ecf.jaxrs.jersey.server.uri=http://localhost:8181/jersey, ecf.rsvc.id=1, endpoint.framework.uuid=89de79e0-b2d7-4953-818c-0bb9e80ae731, endpoint.id=ad3759b5-637b-43c5-b6ce-7d16b562a817, endpoint.package.version.com.xxxx.example=0.0.1.SNAPSHOT, endpoint.service.id=181, objectClass=[Ljava.lang.String;@5903531c, remote.configs.supported=[Ljava.lang.String;@2d08c446, remote.intents.supported=[Ljava.lang.String;@7836b24c, service.imported=true, service.imported.configs=[Ljava.lang.String;@15f7399}]. Remote service NOT IMPORTED;severity4;exception=org.eclipse.ecf.osgi.services.remoteserviceadmin.SelectContainerException: No remote service container selected for endpoint=ECFEndpointDescription[{ecf.endpoint.id=http://localhost:8181/jersey, ecf.endpoint.id.ns=ecf.namespace.jaxrs, ecf.endpoint.ts=1501620321763, ecf.generic.server.hostname=localhost, ecf.generic.server.port=4445, ecf.jaxrs.jersey.server.uri=http://localhost:8181/jersey, ecf.rsvc.id=1, endpoint.framework.uuid=89de79e0-b2d7-4953-818c-0bb9e80ae731, endpoint.id=ad3759b5-637b-43c5-b6ce-7d16b562a817, endpoint.package.version.com.yyyy.api.example=0.0.1.SNAPSHOT, endpoint.service.id=181, objectClass=[Ljava.lang.String;@5903531c, remote.configs.supported=[Ljava.lang.String;@2d08c446, remote.intents.supported=[Ljava.lang.String;@7836b24c, service.imported=true, service.imported.configs=[Ljava.lang.String;@15f7399}]. Remote service NOT IMPORTED;children=[]]
!STACK 0
org.eclipse.ecf.osgi.services.remoteserviceadmin.SelectContainerException: No remote service container selected for endpoint=ECFEndpointDescription[{ecf.endpoint.id=http://localhost:8181/jersey, ecf.endpoint.id.ns=ecf.namespace.jaxrs, ecf.endpoint.ts=1501620321763, ecf.generic.server.hostname=localhost, ecf.generic.server.port=4445, ecf.jaxrs.jersey.server.uri=http://localhost:8181/jersey, ecf.rsvc.id=1, endpoint.framework.uuid=89de79e0-b2d7-4953-818c-0bb9e80ae731, endpoint.id=ad3759b5-637b-43c5-b6ce-7d16b562a817, endpoint.package.version.com.yyyyy.example=0.0.1.SNAPSHOT, endpoint.service.id=181, objectClass=[Ljava.lang.String;@5903531c, remote.configs.supported=[Ljava.lang.String;@2d08c446, remote.intents.supported=[Ljava.lang.String;@7836b24c, service.imported=true, service.imported.configs=[Ljava.lang.String;@15f7399}]. Remote service NOT IMPORTED
at org.eclipse.ecf.osgi.services.remoteserviceadmin.RemoteServiceAdmin.importService(RemoteServiceAdmin.java:456)
at org.eclipse.ecf.osgi.services.remoteserviceadmin.AbstractTopologyManager.handleECFEndpointAdded(AbstractTopologyManager.java:301)
at org.eclipse.ecf.internal.osgi.services.distribution.BasicTopologyManagerImpl.handleEndpointAdded(BasicTopologyManagerImpl.java:107)
at org.eclipse.ecf.internal.osgi.services.distribution.BasicTopologyManagerImpl.endpointChanged(BasicTopologyManagerImpl.java:176)
at org.eclipse.ecf.internal.osgi.services.distribution.Activator$ProxyEndpointEventListener.deliverSafe(Activator.java:206)
at org.eclipse.ecf.internal.osgi.services.distribution.Activator$ProxyEndpointEventListener.endpointChanged(Activator.java:183)
at org.eclipse.ecf.osgi.services.remoteserviceadmin.EndpointDescriptionLocator$1.dispatchEvent(EndpointDescriptionLocator.java:219)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
[/code]

From this, it appears to me that the jersey/jaxrs client provider isn't installed on the Eclipse client. That's essentially the meaning of:

org.eclipse.ecf.osgi.services.remoteserviceadmin.RemoteServiceAdmin:importService:No remote service container selected for endpoint=...

i.e. when it tries to import the service, it can't find the appropriate jersey/jaxrs client distribution provider.

@Component(immediate=true)
	public class HelloWorldClient {

		@Reference(cardinality=ReferenceCardinality.AT_LEAST_ONE,policy=ReferencePolicy.DYNAMIC)
		void bindTimeService(HelloWorldService helloWorldService) {
			System.out.println("Discovered HelloWorldService via DS");
			String message = helloWorldService.getMessage();
			 System.out.println("Message received is: " + message);
		}
		
		void unbindTimeService(HelloWorldService helloWorldService) {
			System.out.println("Undiscovered HelloWorldService via DS");
		}
	}

Scott Lewis wrote on Wed, 02 August 2017 01:49

From this, it appears to me that the jersey/jaxrs client provider isn't installed on the Eclipse client. That's essentially the meaning of:

org.eclipse.ecf.osgi.services.remoteserviceadmin.RemoteServiceAdmin:importService:No remote service container selected for endpoint=...

i.e. when it tries to import the service, it can't find the appropriate jersey/jaxrs client distribution provider.

Cool. That was exactly the reason. It works as expected now. Thanks a lot for your support.
- Service hosted in Karaf offers JAX-RS and Generic Endpoints
- Webclient communicates with the service usingREST
- Eclipse client communicates using OSGi

Just one question that still remains.
From my eclipse client I am not interested in JAX-RS.

All I do is

@Component(immediate=true)
	public class HelloWorldClient {

		@Reference(cardinality=ReferenceCardinality.AT_LEAST_ONE,policy=ReferencePolicy.DYNAMIC)
		void bindTimeService(HelloWorldService helloWorldService) {
			System.out.println("Discovered HelloWorldService via DS");
			String message = helloWorldService.getMessage();
			 System.out.println("Message received is: " + message);
		}
		
		void unbindTimeService(HelloWorldService helloWorldService) {
			System.out.println("Undiscovered HelloWorldService via DS");
		}
	}

Why did I have to install JAX-RS provider in my eclipse client to get rid of the exception in my previous post?