You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2015/04/09 20:19:12 UTC

[jira] [Closed] (AIRAVATA-894) [GSoC-2013] Wrapp all JavaScript registry calls under AiravataJSClient

     [ https://issues.apache.org/jira/browse/AIRAVATA-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suresh Marru closed AIRAVATA-894.
---------------------------------
    Resolution: Won't Fix

Since Airavata is using thrift based API's these issues are not directly relavent now. 

> [GSoC-2013] Wrapp all JavaScript registry calls under AiravataJSClient
> ----------------------------------------------------------------------
>
>                 Key: AIRAVATA-894
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-894
>             Project: Airavata
>          Issue Type: New Feature
>            Reporter: Shameera Rathnayaka
>             Fix For: WISHLIST
>
>         Attachments: AiravatJSClient.patch, AiravataJSClient_resolve.patch
>
>
> At the moment there are eight registry clients with JavaScript registryAPI, and Front-end developer need to know which registry client do the relevant registry rest call to backend. Here suggest to provide one client which can use to do all registry rest calls of these eight registry clients.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)