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

Reply via email to