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

Posted to dev@airavata.apache.org by "Raminderjeet Singh (JIRA)" <ji...@apache.org> on 2014/03/28 16:22:20 UTC

[jira] [Updated] (AIRAVATA-439) GFAC/Orchestrator exception handling and notifications

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

Raminderjeet Singh updated AIRAVATA-439:
----------------------------------------

    Summary: GFAC/Orchestrator exception handling and notifications  (was: GFAC exception handling and notifications)

> GFAC/Orchestrator 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)