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 2012/05/30 16:49:24 UTC

[jira] [Created] (AIRAVATA-434) Why we need to create an object of ProviderException in GramProvider to handle throw?

Raminderjeet Singh created AIRAVATA-434:
-------------------------------------------

             Summary: Why we need to create an object of ProviderException in GramProvider to handle throw?
                 Key: AIRAVATA-434
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-434
             Project: Airavata
          Issue Type: Question
            Reporter: Raminderjeet Singh


Currently we create a object of provider exception and then have a boolean flag to handle the throw. Why not to directly throw exception? 

ProviderException pe = new ProviderException(""); 

Any reason of doing this? I would like to clean this up if no objections. 


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (AIRAVATA-434) Why we need to create an object of ProviderException in GramProvider to handle throw?

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AIRAVATA-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake resolved AIRAVATA-434.
-----------------------------------------

    Resolution: Fixed

Fixed in branch and turnk fix will be done soon.

Lahiru
                
> Why we need to create an object of ProviderException in GramProvider to handle throw?
> -------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-434
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-434
>             Project: Airavata
>          Issue Type: Question
>            Reporter: Raminderjeet Singh
>
> Currently we create a object of provider exception and then have a boolean flag to handle the throw. Why not to directly throw exception? 
> ProviderException pe = new ProviderException(""); 
> Any reason of doing this? I would like to clean this up if no objections. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (AIRAVATA-434) Why we need to create an object of ProviderException in GramProvider to handle throw?

Posted by "Raminderjeet Singh (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AIRAVATA-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raminderjeet Singh reopened AIRAVATA-434:
-----------------------------------------


This is not related to the patch. Lahiru may have patch related JIRA ID's
                
> Why we need to create an object of ProviderException in GramProvider to handle throw?
> -------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-434
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-434
>             Project: Airavata
>          Issue Type: Question
>            Reporter: Raminderjeet Singh
>
> Currently we create a object of provider exception and then have a boolean flag to handle the throw. Why not to directly throw exception? 
> ProviderException pe = new ProviderException(""); 
> Any reason of doing this? I would like to clean this up if no objections. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (AIRAVATA-434) Why we need to create an object of ProviderException in GramProvider to handle throw?

Posted by "Saminda Wijeratne (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AIRAVATA-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290179#comment-13290179 ] 

Saminda Wijeratne commented on AIRAVATA-434:
--------------------------------------------

Applied patch in trunk
Committed revision 1346914.

                
> Why we need to create an object of ProviderException in GramProvider to handle throw?
> -------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-434
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-434
>             Project: Airavata
>          Issue Type: Question
>            Reporter: Raminderjeet Singh
>
> Currently we create a object of provider exception and then have a boolean flag to handle the throw. Why not to directly throw exception? 
> ProviderException pe = new ProviderException(""); 
> Any reason of doing this? I would like to clean this up if no objections. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira