[jira] Issue Comment Edited: (GERONIMODEVTOOLS-580) Servlet/JSP update forces a complete redeploy of a WAR

["Delos Dai (JIRA)" <ji...@apache.org>]

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

Delos Dai edited comment on GERONIMODEVTOOLS-580 at 6/21/09 11:00 PM:
----------------------------------------------------------------------

Ivan, thanks for your information from the perspective of Geronimo server.  So in-place option may reduce the time for copying. But I have concerns about the in-place option.
1) If we're sure most time is spent on copying, then the option will be helpful to reduce the redeploy time. But I'm not sure copying takes up most of the redeploy time. 
2) If in-place option is applied in GEP,  it only applies to the WAR project and EAR project. EJB project can't get  much benifit from the in-place option, because all classes in EJB project has been deployed as a JAR package, as a result, here is only packaging process  instead of copying process. In this way, even in-place option is enabled, the packaging time can't be skipped,  

Besides the copying time, a delta redeploy may be more helpful. But just as Ivan said, Geronimo server only support JSP updating, so at most GEP can only support the delta redeploy for JSP files.

      was (Author: delos):
    Ivan, thanks for your information from the perspective of Geronimo server.  So in-place option may reduce the time for copying. If we're sure much time is spent on copying, then the option will be helpful to reduce the redeploy time. 
  
> Servlet/JSP update forces a complete redeploy of a WAR
> ------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-580
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580
>             Project: Geronimo-Devtools
>          Issue Type: Improvement
>    Affects Versions: 2.0.x, 2.2.0
>            Reporter: Kevan Miller
>            Assignee: Tim McConnell
>             Fix For: 2.2.0
>
>
> I've had several users comment to me that application development with GEP is not as fast as it should be. Basic scenario is create an application, deploy, test, update, test, update, etc... IIUC, for each update, GEP is repackaging the WAR and running a redeploy. Repackaging/redeploy can take some time (for large apps > 30 seconds). IIUC, we could be updating the appropriate JSP/Servlet classes directly and greatly improving this behavior. I don't know how this works, however. Anybody interested in looking at this? I'd like to see this improved in 2.2. If it's something that could be fixed in 2.1.x, that would be great. But that might depend on how extensive the changes are...  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.