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 5DC5910D07 for ; Fri, 28 Mar 2014 15:22:31 +0000 (UTC) Received: (qmail 88487 invoked by uid 500); 28 Mar 2014 15:22:28 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 88397 invoked by uid 500); 28 Mar 2014 15:22:24 -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 88090 invoked by uid 99); 28 Mar 2014 15:22:20 -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:22:20 +0000 Date: Fri, 28 Mar 2014 15:22:20 +0000 (UTC) From: "Raminderjeet Singh (JIRA)" To: dev@airavata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRAVATA-439) GFAC exception handling and notifications 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-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raminderjeet Singh updated AIRAVATA-439: ---------------------------------------- Fix Version/s: 0.13 > GFAC exception handling and notifications > ----------------------------------------- > > Key: AIRAVATA-439 > URL: https://issues.apache.org/jira/browse/AIRAVATA-439 > Project: Airavata > Issue Type: Story > Reporter: Raminderjeet Singh > Assignee: Lahiru Gunathilake > Fix For: 0.13 > > > 1. Currently GFAC have ProviderException, ToolException, GFACException etc. All of them have same methods or a minor variations. These need to be merged or defined properly for developer to use. > 2. Error notification should be handled using a central method. Rest of the components are responsible for throwing useful exceptions and is handled at single place. -- This message was sent by Atlassian JIRA (v6.2#6252)