Difference between revisions of "Package Repository"
(→Implentation Overview) |
(→Introduction) |
||
| Line 3: | Line 3: | ||
=== Introduction === | === Introduction === | ||
| − | The Package Repository validates, stores, and manages DILIGENT packages | + | The Package Repository validates, stores, and manages DILIGENT packages. It checks packages dependencies and giving both access to packages relations and access to the stored packages supports the dynamic packages deployment. |
| + | |||
| + | This repository accepts registration requests coming from the Service Archive Registration Protlet that is part of the VDL service, whilst accepts access requests from the DL service and the HNM service. | ||
=== Implentation Overview === | === Implentation Overview === | ||
Revision as of 16:15, 14 September 2007
Contents
Package Repository
Introduction
The Package Repository validates, stores, and manages DILIGENT packages. It checks packages dependencies and giving both access to packages relations and access to the stored packages supports the dynamic packages deployment.
This repository accepts registration requests coming from the Service Archive Registration Protlet that is part of the VDL service, whilst accepts access requests from the DL service and the HNM service.
Implentation Overview
This component is responsible for the validation, storage, and maintenance of the DILIGENT service archives, each service archive contains all files declared on the Service Profile . It checks packages dependencies and by ensuring access to them, it supports the dynamic packages deployment.
The Package Repository is a WSRF service, implemented as specified by the Singleton Pattern . Accordingly, it splits the implementation into three sub-components: (i) the resource itself that contains Package Repository state, (ii) the resource home that manages the resource, and (iii) the web service that gives access to components functionality.
The resource state contains information about the stored service archives. The resource home is used by the web service to create and find the resource.
The web service provides to the clients, e.g. HNM, access to the Package Repository functionality (see Section 3.2.1.3 below). A Service Archive has the following structure:
