airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eroma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AIRAVATA-1146) Seperate out the Derby Server Startup from the Airavata API Server Startup
Date Thu, 18 Jun 2015 14:44:24 GMT

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

Eroma closed AIRAVATA-1146.
---------------------------
    Resolution: Not A Problem

> 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
>             Fix For: 0.15 
>
>
> 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)

Mime
View raw message