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.
Difference between revisions of "Swordfish Documentation: Architecture: Service Registry Plugin"
Line 1: | Line 1: | ||
− | == | + | == Description (under construction) == |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
The Service Registry Plugin consists of the following components: | The Service Registry Plugin consists of the following components: | ||
<ul> | <ul> | ||
Line 20: | Line 11: | ||
<li>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.</li> | <li>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.</li> | ||
</ol> | </ol> | ||
+ | |||
+ | <h1>Component diagrams</h1> | ||
+ | |||
+ | == Public API for the Service Registry Resolving component (under construction) == | ||
+ | [[Image:RegistryAPIPackage.png]] | ||
+ | |||
+ | == Sketch of сomponent сlasses for Service Endpoint Resolution (under construction) == | ||
+ | [[Image:ServiceRegistryCommunicationComponents.png]] | ||
+ | |||
+ | == Sketch of Service Endpoint Resolution sequence: (under construction) == | ||
+ | [[Image:EndpointResolution.png]] |
Revision as of 08:17, 26 March 2009
Contents
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:
- 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.