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

Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2015/04/09 21:54:14 UTC

[jira] [Updated] (AIRAVATA-1146) Seperate out the Derby Server Startup from the Airavata API Server Startup

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

Eroma updated AIRAVATA-1146:
----------------------------
    Assignee: Chathuri Wimalasena

> Seperate out the Derby Server Startup from the Airavata API Server Startup
> --------------------------------------------------------------------------
>
>                 Key: AIRAVATA-1146
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1146
>             Project: Airavata
>          Issue Type: Task
>            Reporter: Saminda Wijeratne
>            Assignee: Chathuri Wimalasena
>
> Currently the Airavata API Server starts up the derby server before it starts itself. The derby server will be redundant in case of trying to use an existing server hosted elsewhere. Thus Derby server startup/shutdown etc. should be refactored in to a new server so that users can give the option to to start or not the derby server.
> Airavata API Server startup is handled in class org.apache.airavata.api.server.AiravataAPIServer



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)