You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2009/06/19 14:35:07 UTC
[jira] Created: (GERONIMODEVTOOLS-580) Servlet/JSP update forces a
complete redeploy of a WAR
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.
[jira] Updated: (GERONIMODEVTOOLS-580) Servlet/JSP update forces a
complete redeploy of a WAR
Posted by "Delos Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Delos Dai updated GERONIMODEVTOOLS-580:
---------------------------------------
Attachment: 580.patch
replace previous patch with updated wording in dialog.
> 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
>
> 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.
[jira] Issue Comment Edited: (GERONIMODEVTOOLS-580) Servlet/JSP
update forces a complete redeploy of a WAR
Posted by "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.
[jira] Commented: (GERONIMODEVTOOLS-580) Servlet/JSP update forces
a complete redeploy of a WAR
Posted by "Delos Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722450#action_12722450 ]
Delos Dai commented on GERONIMODEVTOOLS-580:
--------------------------------------------
I think the key to this problem is whether the problem exist in GEP or in Geronimo server, In fact, redeploy with GEP will invoke the redeploy function of Geronimo server. So in my opinion, the most time-consuming work is done by server inteadof GEP. However, it's better to find a way to speed up the redeploy process. For this, we need to figure out if there is any useful mechanism of Geronimo server? Maybe making use of hot deploy in Geronimo Server is an option. But I'm not sure how helpful will it be?
Any comments?
> 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.
[jira] Commented: (GERONIMODEVTOOLS-580) Servlet/JSP update forces
a complete redeploy of a WAR
Posted by "Delos Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723411#action_12723411 ]
Delos Dai commented on GERONIMODEVTOOLS-580:
--------------------------------------------
Maybe GEP can try local jsp file hot replacement first, making use of Geronimo server development mode.
> 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.
[jira] Commented: (GERONIMODEVTOOLS-580) Servlet/JSP update forces
a complete redeploy of a WAR
Posted by "viola.lu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736999#action_12736999 ]
viola.lu commented on GERONIMODEVTOOLS-580:
-------------------------------------------
Hi, Delos:
I enabled this function in Geronimo Eclipse Plugin, and try to modify context-root of a web app, for example, change <web:context-root>/cviewer </web:context-root> to <web:context-root>/cview</web:context-root> but its change will not be updated to server.
Pls check it, thanks.
> 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.
[jira] Commented: (GERONIMODEVTOOLS-580) Servlet/JSP update forces
a complete redeploy of a WAR
Posted by "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 commented on GERONIMODEVTOOLS-580:
--------------------------------------------
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.
[jira] Closed: (GERONIMODEVTOOLS-580) Servlet/JSP update forces a
complete redeploy of a WAR
Posted by "Delos Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Delos Dai closed GERONIMODEVTOOLS-580.
--------------------------------------
Verified it, All the problems have been resolved,so close it.
> 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.
[jira] Commented: (GERONIMODEVTOOLS-580) Servlet/JSP update forces
a complete redeploy of a WAR
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722456#action_12722456 ]
Ivan commented on GERONIMODEVTOOLS-580:
---------------------------------------
For the JSP files, after changing the settings in Tomcat's configuration files, we could make it take effect once we changed without deployment. For the Servlet classes, currently, I think, the redployment action is must, Geronimo needs to re-analysis those classes, for example, user may add a WebService annotation for it. I know that the Server has a in-place option, with it, no copy action is need in the redeployment process, so it may reduce the time effor.
The possible solution is that, in GEP, the user could turn on the in-place option and JSP debug option, while the user changes those files, if they are of JSP type, then no action is taken. If they are of Java classes, redeploy the app.
> 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.
[jira] Resolved: (GERONIMODEVTOOLS-580) Servlet/JSP update forces a
complete redeploy of a WAR
Posted by "Tim McConnell (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMODEVTOOLS-580) Servlet/JSP update forces
a complete redeploy of a WAR
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722519#action_12722519 ]
David Jencks commented on GERONIMODEVTOOLS-580:
-----------------------------------------------
A really really long time ago we had the idea of enhancing the in-place deployment so that it didn't need a properly structured javaee app but instead had some kind of location map that could point into the internal structure of an eclipse project (or idea, or maven....) I think the original GEP developer worked on this a bit but I don't know how far he got.
If we can do this then jasper ought to be able to notice whenever a jsp is changed and recompile it.
For classes, I think I heard there is a java6 feature that lets you relead modified classes. This obviously won't help if you add or remove annotations or interface members but for small code changes it ought to be able to help speed up debugging. I have no idea how practical this class reloading actually is :-)
Hot deploy won't help as it is just a slow unreliable way of triggering a normal full deployment.
> 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.
[jira] Issue Comment Edited: (GERONIMODEVTOOLS-580) Servlet/JSP
update forces a complete redeploy of a WAR
Posted by "Delos Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723411#action_12723411 ]
Delos Dai edited comment on GERONIMODEVTOOLS-580 at 6/24/09 12:59 AM:
----------------------------------------------------------------------
Seems in-place option has not been implemented yet in GEP. Maybe GEP can try local jsp file hot replacement first, making use of Tomcat development mode.
was (Author: delos):
Maybe GEP can try local jsp file hot replacement first, making use of Geronimo server development mode.
> 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.
[jira] Commented: (GERONIMODEVTOOLS-580) Servlet/JSP update forces
a complete redeploy of a WAR
Posted by "Delos Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737399#action_12737399 ]
Delos Dai commented on GERONIMODEVTOOLS-580:
--------------------------------------------
Hi Viola,
I have fixed your problem with revision #799490.
Thanks for you verification!
> 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.
[jira] Updated: (GERONIMODEVTOOLS-580) Servlet/JSP update forces a
complete redeploy of a WAR
Posted by "Delos Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Delos Dai updated GERONIMODEVTOOLS-580:
---------------------------------------
Attachment: (was: 580.patch)
> 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.
[jira] Updated: (GERONIMODEVTOOLS-580) Servlet/JSP update forces a
complete redeploy of a WAR
Posted by "Delos Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Delos Dai updated GERONIMODEVTOOLS-580:
---------------------------------------
Attachment: 580.patch
Hi,
I create a patch for this JIRA. It provide an option "Not redeploy JSP files" in server instance. If this option is selected, then JSP update in normal Web project won't trigger a redeploy, instead, it will just copy the jsp files to target position.
But there are some limitations for this
1) It only works for local server
2) Besides the option, user has to set "development" of "JSPServlet" in catalina.xml to "true"
Could anyone help to review it?
Thanks a lot!
> 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
>
> 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.
[jira] Commented: (GERONIMODEVTOOLS-580) Servlet/JSP update forces
a complete redeploy of a WAR
Posted by "Delos Dai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735259#action_12735259 ]
Delos Dai commented on GERONIMODEVTOOLS-580:
--------------------------------------------
Tim,
Thanks very much for your help!
I agree with you on the two improvements.
I will try Jetty configuration and record it in document. For the "development" mode, once Jetty configuration is figured out, I will try to make the update automatic
> 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.