Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D5E910C32 for ; Fri, 28 Mar 2014 15:10:17 +0000 (UTC) Received: (qmail 48519 invoked by uid 500); 28 Mar 2014 15:10:16 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 48467 invoked by uid 500); 28 Mar 2014 15:10:15 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 48454 invoked by uid 99); 28 Mar 2014 15:10:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Mar 2014 15:10:15 +0000 Date: Fri, 28 Mar 2014 15:10:15 +0000 (UTC) From: "Lahiru Gunathilake (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AIRAVATA-480) Improve the GFac API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRAVATA-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AIRAVATA-480. ----------------------------------------- Resolution: Fixed These are resolved in new gfac implementation. > Improve the GFac API > -------------------- > > Key: AIRAVATA-480 > URL: https://issues.apache.org/jira/browse/AIRAVATA-480 > Project: Airavata > Issue Type: Sub-task > Reporter: Milinda Lakmal Pathirage > > InvocationContext, ExecutionContext, MessageContext has confusing meanings and usages inside GFac API. Current extension mechanism API is somewhat confusing. We need to fix those. -- This message was sent by Atlassian JIRA (v6.2#6252)