[
https://issues.apache.org/jira/browse/ARIES-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502951#comment-15502951
]
Christian Schneider commented on ARIES-1613:
--------------------------------------------
You can set the httpBase to any address. It is simply what is prefixed to the
relative service address when publishing the endpoint address. So if you are
fine with only having this prefix for all services of this host then it should
work fine.
You can not solve the zone problem with httpBase and you can also not solve it
with the discoveryPlugin. In both cases you would not be able to let some
clients see one address and some the other.
The bridge solution should be doable but would require custom code for the
bridge. You would simply need to watch the backend zookeeper and update the
frontend zookeeper. The current discovery code should provide a good starting
point for this. Maybe we can make the zookeeper discovery more flexible so you
can set it up to listen to one zookeeper and publish to another. That could
then be the basis for a bridge.
I will create a discussion on aries dev on the topic of zones and how we could
support them.
> 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
(v6.3.4#6332)
