Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Swordfish Documentation: Architecture: Service Registry Plugin

Revision as of 08:14, 26 March 2009 by Unnamed Poltroon (Talk)

Public API for the Service Registry Resolving component (under construction)

RegistryAPIPackage.png

Sketch of сomponent сlasses for Service Endpoint Resolution (under construction)

ServiceRegistryCommunicationComponents.png

Sketch of Service Endpoint Resolution sequence: (under construction)

EndpointResolution.png

Component Description (under construction)

The Service Registry Plugin consists of the following components:

  • ServiceResolver - resolves information about the service endpoints for specified service using endpoint document providers and endpoint extractors
  • EndpointDocumentProvider - is responsible for retrieval of service related information (e.g. service descriptions) from different kinds of location
  • EndpointExtractor - extracts endpoint parts (endpoint address, transport protocol) from the service description document


The endpoint resolution process is illustrated by the folowing scenario:

  1. First ServiceResolver gets all registered EndpointDocumentProviders and chooses one with highest priority. Different implementation of the EndpointDocumentProvider can be used to retrieve the service descriptions from local filesystem or from a remote registry. The chosen provider is then queried for service description documents corresponding to the specified service interface.

Back to the top