airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Supun Chathuranga Nakandala (JIRA)" <>
Subject [jira] [Closed] (AIRAVATA-409) Documenting the Registry CPI
Date Fri, 11 Dec 2015 21:20:46 GMT


Supun Chathuranga Nakandala closed AIRAVATA-409.
    Resolution: Fixed

Not relevant in the current version

> Documenting the Registry CPI
> ----------------------------
>                 Key: AIRAVATA-409
>                 URL:
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Workflow Interpreter
>            Reporter: Saminda Wijeratne
>            Assignee: Supun Chathuranga Nakandala
>              Labels: Contributor
>             Fix For: 1.0
> 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 was sent by Atlassian JIRA

View raw message