[jira] [Created] (ARIES-2216) Better-define the exported service properties that define a unique endpoint

["Amichai Rothman (Jira)" <ji...@apache.org>]

Amichai Rothman created ARIES-2216:
--------------------------------------

             Summary: Better-define the exported service properties that define a unique endpoint
                 Key: ARIES-2216
                 URL: https://issues.apache.org/jira/browse/ARIES-2216
             Project: Aries
          Issue Type: Bug
          Components: Remote Service Admin
    Affects Versions: rsa-1.16.1
            Reporter: Amichai Rothman


When exporting a service, RemoteServiceAdminCore either creates a new endpoint and returns a new export registration, or, if the endpoint already exists, it returns a copy of the export registration that is linked to the existing endpoint. This is according to the spec.

Currently, in order to lookup existing registrations, it uses the entire map of service properties as the unique key for the endpoint. However, if any service property changes, even one that is part of how the service normally operates and is completely unrelated to RSA or the export configuration, this will be considered a new endpoint with a new registration. This also means service property updates never get propagated remotely as they should, and instead only new endpoints are added on every change.

The key used in looking up existing registrations needs to be narrowed down, ideally containing only export-related properties that should trigger the creation of a new endpoint, and ignoring custom service properties that should be propagated for an existing endpoint and not signal that it is a separate export.

One heuristic for this might be to look for properties with specific prefixes, e.g. service.* which includes all RSA import/export properties and service-unique properties, and properties whose prefix is the distribution provider config type, which according to the spec should be the prefix to all endpoint implementation-specific properties.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)