Panu Hämäläinen commented on ARIES-1613:

Is it ok to set httpBase (in HttpServiceManager) to a host and port, as well as 
an additional context path, which the back-end host itself actually does not 
listen to (i.e. to the host (interface address), port and context path of the 
front-end proxy)? Or, does httpBase have some dependency on the OSGi HTTP 
service (or, Jetty) configuration (its interface, port, Jetty connectors)?

If moving to TopologyManager would support the same functionality as Zookeeper 
DiscoveryPlugin now does, I am fine with the move.

Yes, some sort of zone support would be great: setting httpBase will not fully 
do since I would also like to be able to call the services with the real 
back-end address with possible clients (e.g. other services on other servers) 
in the back-end ("internal") network and with the proxied (SSL) address with 
the clients from outside ("external network"). And for both cases I would like 
to use (Zookeeper) service discovery for resolving the service addresses.

For the proxy technology, I have thinking of Apache HTTPD for now.

Two zookeepers, filtering, bridge, DOSGi-aware proxy: is something like this 
already possible with the current versions of the needed technologies?

We can move (or can you move) the discussion to the dev list if Jira is not the 
correct place to continue.

> DiscoveryPlugin interface not exported
> --------------------------------------
>                 Key: ARIES-1613
>                 URL: https://issues.apache.org/jira/browse/ARIES-1613
>             Project: Aries
>          Issue Type: Bug
>          Components: Remote Service Admin
>    Affects Versions: rsa-1.9.0
>            Reporter: Panu Hämäläinen
> The package containing the interface 
> org.apache.cxf.dosgi.discovery.zookeeper.publish.DiscoveryPlugin is not 
> exported (MANIFEST.MF) from bundle cxf-dosgi-ri-discovery-distributed (1.7.0) 
> which makes it impossible to implement 3rd party discovery plugins.

This message was sent by Atlassian JIRA

Reply via email to