[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ecf-dev] Problem with Remote Services
|
Hi Wojciech,
Wojciech Galanciak wrote:
Maybe, but the same parameter must be set during service registration
on the host
The REMOTE_INTERFACE property is set during service registration on the
host:
// add OSGi service property indicating this
props.put(REMOTE_INTERFACES, REMOTE_INTERFACES_WILDCARD);
and in the filter definition in the consumer (now in host is
REMOTE_INTERFACE and in consumer is REMOTE).
As I read the current RFC119, it indicates that the required property
REMOTE_INTERFACE (osgi.remote.interfaces) is set on the host, and the
REMOTE (osgi.remote) is set on the consumer/proxy.
Scott
2009/6/2 Scott Lewis <slewis@xxxxxxxxxxxxxxxxx
<mailto:slewis@xxxxxxxxxxxxxxxxx>>
Hi Wojciech,
Wojciech Galanciak wrote:
I found a small bug in filter declaration:
context.createFilter("(&("+org.osgi.framework.Constants.OBJECTCLASS+"="
+ IHello.class.getName() +")(" + REMOTE + "=*))");
There should be REMOTE_INTEFACE instead of REMOTE.
I think this property (REMOTE) is correct. The idea here is that
for the consumer the service found should have the "osgi.remote"
property set to any value. The RFC119 spec has "osgi.remote"
currently mean that the service is a remote proxy. The intention
here is to only detect services that are registered as remote (not
locally registered ones).
Scott
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx <mailto: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