[ 
https://issues.apache.org/jira/browse/ARIES-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503266#comment-15503266
 ] 

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

Maybe the part "As we currently do not have a way to use the discoveryPlugin it 
would be easy to remove it completely and move this functionality to 
TopologyManager" should be handled with this bug report (or, create another 
copy report under DOSGi) and the more advanced topics (zones) in the dev list.

I think I would still need something else, i.e. DiscoveryPlugin-like support in 
TopologyManager, than setting only httpBase. I would like to select which 
services are published at the proxy address and which at the direct address. I 
could implement the selection logic by e.g. defining a custom service property 
which I check when TopologyManager calls my "TopologyManager-DiscoveryPlugin", 
and/or inspect the context of the service address in the TopologyManager-plugin 
(e.g. if it is /public/something, it should be published to the proxy address).

> 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)

Reply via email to