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