geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (Commented) (JIRA)" <>
Subject [jira] [Commented] (GERONIMODEVTOOLS-790) Application started twice
Date Tue, 20 Mar 2012 17:09:39 GMT


Jarek Gawor commented on GERONIMODEVTOOLS-790:

I committed a first attempt at this feature in revision 1302954 (gep) and revision 1302962
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:

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

> Application started twice
> -------------------------
>                 Key: GERONIMODEVTOOLS-790
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message