Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Tue, 20 Mar 2012 17:09:39 +0000 (UTC)
From: "Jarek Gawor (Commented) (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: 
 <2018383266.37130.1332263379070.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1111352502.33032.1332191620530.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (GERONIMODEVTOOLS-790) Application started twice
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jarek Gawor commented on GERONIMODEVTOOLS-790:
----------------------------------------------

I committed a first attempt at this feature in revision 1302954 (gep) and revision 1302962 (server).
GEP will figure out a list of modified configuration ids and pass them to the server (when launching the server) using the "geronimo.loadOnlyConfigList" system property. On startup, the server will load the configurations on this list but will not start them. That will enable GEP to redeploy & start the application once the server is fully started. 

Right now this feature is disabled in GEP by default. To enable it, set the following system property in ecplise.init:

-Dorg.apache.geronimo.st.v30.core.manageApplicationStart=true

As mentioned above, this feature will only work if the server is started via GEP.

                
> Application started twice
> -------------------------
>
>                 Key: GERONIMODEVTOOLS-790
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-790
>             Project: Geronimo-Devtools
>          Issue Type: New Feature
>          Components: eclipse-plugin
>    Affects Versions: 3.0-beta-1
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>
> Say we have an application that is already deployed to the server and the server is stopped. Now, the application is modified while the server is stopped and server restarted. What happens is that when server starts up, it will start the "old" version of the application. And after the server is full started, Eclipse will automatically deploy the "new" application. That's usuallly ok but if you are dealing with large applications or applications that take some time to initialize that's very painful. 
> So the idea here is that when such case happens only the "new" version of the application is deployed.

--
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