Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Date: Sun, 26 Jan 2014 17:43:38 +0000 (UTC)
From: "Shameera Rathnayaka (JIRA)" <jira@apache.org>
To: dev@airavata.apache.org
Message-ID: <JIRA.12617010.1353446529436.15747.1390758218031@arcas>
In-Reply-To: <JIRA.12617010.1353446529436@arcas>
References: <JIRA.12617010.1353446529436@arcas>
Subject: [jira] [Commented] (AIRAVATA-651) Change XBaya Workflow Launches to
 use Airavata Client API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AIRAVATA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882368#comment-13882368 ] 

Shameera Rathnayaka commented on AIRAVATA-651:
----------------------------------------------

Hi Suresh, 

Is this still valid issue? , As i can see, workflow interpreter module has been removed from build.

Thanks, 
Shameera. 

> Change XBaya Workflow Launches to use Airavata Client API
> ---------------------------------------------------------
>
>                 Key: AIRAVATA-651
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-651
>             Project: Airavata
>          Issue Type: Improvement
>            Reporter: Suresh Marru
>
> XBaya is directly using Workflow Interpreter stubs. In a step to unify all Airavata operations through API, need to change Xbaya use the API's. 


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)