[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-580.
--------------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.5
HI Delos, thanks very much for this patch. It is a very good piece of work !!
In my test workspace with 2 web application projects it normally takes 20-25
seconds to redeploy both applications when I modify JSP files in them. With
your enhancement it now takes last then 2 seconds -- very impressive.
With the recommended changes I asked for I committed it to both trunk (797732)
and 2.1.5 (797733). Finally, even though I'm resolving the issue you might want
to consider a couple improvements.
1. See if you can get it to work for Jetty
2. Your message dialog to remind the user to ensure that the JSP compiler is
enabled in development mode is useful, but since you already know the
installation directory of the server you could easily read the necessary
configuration file to see if that parameter is enabled or not. If it is enabled
there is no need to display the message dialog; if it's not enabled, you might
present instead a dialog with Yes and No buttons specifying whether the GEP
should update it on their behalf.
> 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.1.5, 2.2.0
>
> Attachments: 580.patch
>
>
> 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.
