[jira] [Resolved] (AIRAVATA-717) Xbaya does not give any error as a dialog box incase it is not able to connect to Registry

["Suresh Marru (JIRA)" <ji...@apache.org>]

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

Suresh Marru resolved AIRAVATA-717.
-----------------------------------

    Resolution: Won't Fix

New implementations of XBaya are using the app-catalog instead of old registry. Need to test and open new issues with latest architecture. 

> Xbaya does not give any error as a dialog box incase it is not able to connect to Registry
> ------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-717
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-717
>             Project: Airavata
>          Issue Type: Bug
>          Components: XBaya
>    Affects Versions: 0.6
>            Reporter: Raminderjeet Singh
>              Labels: Contributor
>             Fix For: 0.13
>
>
> User is not getting any error if connection to registry fails. Console exception need to be improved also. Only towards the end of error stack its giving connection refused. Error message expected is something like "Not able to connect to registry."
> org.apache.airavata.client.api.AiravataAPIInvocationException: Error invoking API
>         at org.apache.airavata.client.AiravataAPIFactory.getAPI(AiravataAPIFactory.java:55)
>         at org.apache.airavata.client.AiravataAPIFactory.getAPI(AiravataAPIFactory.java:42)
>         at org.apache.airavata.xbaya.ui.dialogs.registry.JCRRegistryWindow.getAiravataAPI(JCRRegistryWindow.java:228)
>         at org.apache.airavata.xbaya.ui.dialogs.registry.JCRRegistryWindow.ok(JCRRegistryWindow.java:115)
>         at org.apache.airavata.xbaya.ui.dialogs.registry.JCRRegistryWindow.access$100(JCRRegistryWindow.java:51)
>         at org.apache.airavata.xbaya.ui.dialogs.registry.JCRRegistryWindow$2.actionPerformed(JCRRegistryWindow.java:204)



--
This message was sent by Atlassian JIRA
(v6.2#6252)