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 3: | Line 3: | ||
<ul> | <ul> | ||
<li>ServiceResolver - resolves information about the service endpoints for specified service using endpoint document providers and endpoint extractors</li> | <li>ServiceResolver - resolves information about the service endpoints for specified service using endpoint document providers and endpoint extractors</li> | ||
| − | <li>EndpointDocumentProvider - is responsible for retrieval of service | + | <li>EndpointDocumentProvider - is responsible for retrieval of service description from different kinds of location. |
Different implementation of the EndpointDocumentProvider can be used to get the service descriptions from local filesystem or from a remote registry.</li> | Different implementation of the EndpointDocumentProvider can be used to get the service descriptions from local filesystem or from a remote registry.</li> | ||
<li>EndpointExtractor - extracts endpoint parts (endpoint address, transport protocol) from the service description document. | <li>EndpointExtractor - extracts endpoint parts (endpoint address, transport protocol) from the service description document. | ||
Revision as of 08:43, 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 description from different kinds of location. Different implementation of the EndpointDocumentProvider can be used to get the service descriptions from local filesystem or from a remote registry.
- EndpointExtractor - extracts endpoint parts (endpoint address, transport protocol) from the service description document. At the same time multiple endpoint extractors can be registered in the system, each suitable for processing one specified type of service description document (e.g. extractor for WSDL 1.1 based service descriptions, extractor for WSDL 2.0 and so on).
The endpoint resolution process can be described by the folowing scenario:
- ServiceResolver gets all EndpointDocumentProviders registered at runtime and chooses one with the highest priority. The chosen provider is then queried for service description documents corresponding to the specified service interface. All found documents are returned from provider as collection of the ServiceDescription objects where each ServiceDescription represents one raw service description document.
- ServiceResolver gets all registered EndpointExtractors and uses them to extract endpoint impormation from received ServiceDescriptions. Extracted information is grouped as collection of EndpointDescription objects and returned to calling context.
Component diagrams
Public API for the Service Registry Resolving component (under construction)
Sketch of сomponent сlasses for Service Endpoint Resolution (under construction)
Sketch of Service Endpoint Resolution sequence: (under construction)
