Timothy Ward commented on ARIES-1613:
> If I understood correctly, "remote Topology Manager" is the one running on
> the remote client, right?
There are two topology managers installed, one on the "server" side and one on
the "client" side.
The "server" topology manager is the one who can add extra properties when
exporting the service, and who gets to decide the following things:
1. Which distribution providers should be used for export
2. What extra properties should be exported alongside the service properties
3. Which endpoint descriptions should be sent to the local Endpoint Event
Listeners in the framework
4. What to do on endpoint faliure
The "client" topology manager receives endpoint notifications from discovery,
which should be passing the Endpoints unadulterated and can:
1. Decide to import, ignore or save an endpoint description for later
2. Decide which distribution provider(s) to try importing the service with
3. What to do on endpoint failure
> it would be nice (at least from security, or hardening, perspective) that
> they did not know anything about (i.e. they do not see) the "raw"
The correct place to do the security check here is in a firewall and/or filter
on the "raw" servlet, to check access is not from outside, otherwise someone
could simply guess the URL. Also, by choosing to ignore the raw URL it remains
invisible as a service (i.e. no imported OSGi service exists).
If you really want to partition your discovery space then what you need are two
discovery providers (or two configurations of the same discovery provider)
which have different discovery domains. Again, these would not change the
endpoint properties, but the server topology can determine which
EndpointEventListener is called for which EndpointDescription.
> 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