Document Actions
3.
Architecture
Up one level
A brief overview of the architecture of a service.
Interfaces
The UML class diagram below shows the key interfaces used in the sample code. The ones with "Sample" in the name are from the dev-kit; the others are from the standard GRIA libraries.
Key Java interfaces
The main interfaces are:
- SampleService
- All service SOAP operations which take no context. For example, operations for creating or discovering resources are defined here.
- SampleResource
- All service SOAP operations with take a sample resource as their context.
These two interfaces correspond to the two SOAP endpoints. Each endpoint has its own WSDL document.
The RemoveSampleService interface defines some extra helper methods on the SampleService
interface, which do not correspond to SOAP operations. There is no corresponding interface for SampleResource as this plugin doesn't add any methods to this.
The interfaces from the core GRIA libraries are:
- GridService
- Operations to get the service's certificates and resources.
- ManagedGridService
- A service managed by an account or SLA service.
- ReportAPI
- A service which can deliver usage reports to an SLA service.
- PolicyManagement
- A resource whose access control rules can be managed.
- WSResourceLifetime
- A resource which can be destroyed, following the WS-ResourceLifetime specification.
- ResourceMetadata
- A resource with a user-set label and other metadata.
- IdentifiableResource
- A resource which can provide a MatchPattern allowing it to be identified.
All the interfaces are described fully in the on-line JavaDoc reference.
