aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Panu Hämäläinen (JIRA) <>
Subject [jira] [Commented] (ARIES-1613) DiscoveryPlugin interface not exported
Date Mon, 19 Sep 2016 07:11:20 GMT


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

ExportPolicy looks like a nice extension. It can be used for adding service properties (e.g.
for exporting a service that itself does not define export) but not for changing the properties
the service has already defined, especially (and only) before they are transferred to Zookeeper
(i.e. my need is to only change the property values visible at Zookeeper). 

I have a use case in which I need to change the base addresses of the back-end OSGi services
advertised at Zookeeper due to a front-end reverse proxy which takes care of SSL. For example,
if a service is exported at back-end server address "http://<back-end-host>:<back-end-port>/myservice",
I need to change the address to "https://<front-end-host>:<front-end-port>/some-context/myservice".
And this change is only needed for the Zookeeper data, not for the actual service properties
at the back-end server hosting/exporting the OSGi service.

> DiscoveryPlugin interface not exported
> --------------------------------------
>                 Key: ARIES-1613
>                 URL:
>             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

View raw message