Hi Jun,
On 9/1/2019 10:29 PM, Scott Lewis wrote:
<stuff delected>
Yes both of these use cases are supported. As an example of 1: during
testing of the DubboProvider I exported a DemoService instances as an
OSGi Remote Service. Since it was exported with the Dubbo protocol,
it can/could be accessed by either an OSGi-based client (as per the
examples in the DubboProvider...i.e. 2) AND I tested access to it via
a Java-only client (from dubbo-demo-api-consumer). What this means
is that such a service can be accessed by any consumer (OSGi or not)
that uses the dubbo protocol (both 1 and 2).
To provide an example of this, I created this java project [1]. It's a
DemoService consumer that is Java-only (similar to your own
dubbo-demo-api-consumer except for how the dubbo url is discovered), but
it can use/call the DemoService exported by the OSGi RS impl [2].
Scott
[1]
https://github.com/ECF/DubboProvider/tree/master/examples/ecf.example.demo.consumer
[2]
https://github.com/ECF/DubboProvider/tree/master/examples/org.eclipse.ecf.examples.provider.dubbo.demo.impl
