[
https://issues.apache.org/jira/browse/AIRAVATA-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saminda Wijeratne reassigned AIRAVATA-409:
------------------------------------------
Assignee: Hasitha Aravinda
> Learning the Registry API
> -------------------------
>
> Key: AIRAVATA-409
> URL: https://issues.apache.org/jira/browse/AIRAVATA-409
> Project: Airavata
> Issue Type: Sub-task
> Components: Workflow Interpreter
> Reporter: Saminda Wijeratne
> Assignee: Hasitha Aravinda
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
