[AIRAVATA-409] Documenting the Registry CPI

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0
• Component/s: Workflow Interpreter
• Labels: Contributor
• Assignee: Supun Nakandala
• Reporter: Saminda
• Created: 10/May/12 14:56
• Updated: 11/Dec/15 21:20
• Resolved: 11/Dec/15 21:20

Description

Airavata uses a registry as a storage for its metadata & userdata. Current implementation of Registry API uses a JCR Registry (Jackrabbit specifically speaking).

For starters look at the following aspects of the Registry API.

1. Type of data that is saved/searched/retrieved through the API

(actually that sort of sums up what the registry API for)

Once you understand the above as a small assignment try to do the following,
1. Try using the API
2. Try to see if you can cluster the functions in the API to groups based on relevance. (eg: functions related to working with workflows, functions related to host descriptions etc.)
3. Check to see if there exist any redundancy of functions defined.
4. If you are given the choice of redefining the API how would you rather do it?

Registry API consists of the following Interfaces
org.apache.airavata.common.registry.api.Registry
org.apache.airavata.registry.api.Axis2Registry
org.apache.airavata.registry.api.DataRegistry

The actual implementation is at,
org.apache.airavata.registry.api.impl.AiravataJCRRegistry