You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Amila Jayasekara (JIRA)" <ji...@apache.org> on 2013/01/04 15:12:12 UTC

[jira] [Commented] (AIRAVATA-663) Add exception to AiravataAPI interface

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

Amila Jayasekara commented on AIRAVATA-663:
-------------------------------------------

Now all manager interfaces (AiravataManager, ApplicationManager, WorkflowManager, ProvenanceManager, ExecutionManager) are throwing AiravataAPIInvocationException or DescriptorRecordAlreadyExistsException in appropriate situations. Exceptions are propagated to user using above mentioned classes.
                
> Add exception to AiravataAPI interface
> --------------------------------------
>
>                 Key: AIRAVATA-663
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-663
>             Project: Airavata
>          Issue Type: Improvement
>          Components: Airavata Client
>            Reporter: Amila Jayasekara
>            Assignee: Amila Jayasekara
>
> Currently interface methods does not have any exceptions. But AiravataAPI is the inerface which clients are using. Therefore we need to propagate error conditions to AiravataAPI through proper exceptions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira