You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2016/09/19 07:57:20 UTC
[jira] [Comment Edited] (ARIES-1613) DiscoveryPlugin interface not
exported
[ https://issues.apache.org/jira/browse/ARIES-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502635#comment-15502635 ]
Christian Schneider edited comment on ARIES-1613 at 9/19/16 7:56 AM:
---------------------------------------------------------------------
Another case might be if you have two or more "zones" in your architecture. In that case there might be a backend zone where the services are addressed directly and a frontend zone where they have to be addressed using a https proxy. In that case we need different endpoint addresses for each zone.
For that case I can imagine that you use two zookeepers (one in backend and one in frontend zone). You would then need a kind of bridge that discovery each service in the backend zone and then can filter which services to offer through the frontend proxy and how to translate these.
The use case above could also be implemented by a DOSGi aware proxy. The proxy could implement the bridge functionality. What proxy do you use? I think it might be interesting to provide a DOSGi extension for one of the popular proxy servers like nginx .. or for one of the popular discoveries like consul.
In any case as the major release is out now it might be a good opportunity to discuss this on the dev list. Maybe we find something better then the zookeeper discoveryPlugin
was (Author: chris@die-schneider.net):
Another case might be if you have two or more "zones" in your architecture. In that case there might be a backend zone where the services are addressed directly and a frontend zone where they have to be addressed using a https proxy. In that case we need different endpoint addresses for each zone.
For that case I can imagine that you use two zookeepers (one in backend and one in frontend zone). You would then need a kind of bridge that discovery each service in the backend zone and then can filter which services to offer through the frontend proxy and how to translate these.
The use case above could also be implemented by a DOSGi aware proxy. The proxy could implement the bridge functionality. What proxy do you use? I think it might be interesting to provide a DOSGi extension for one of the popular proxy servers like nginx.
> 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)