[
http://jira.codehaus.org/browse/CARGO-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178752#action_178752 ]
Amnon Khen commented on CARGO-419:
----------------------------------
Hi,
I also emailed this question to the people that worked on this bug.
It's written hhere that redeploy was implemented as an undeploy followed by a deploy.
Why does Cargo not allow the user to choose what to do? The TomcatManager class allows the user to choose whether to use the 'update' request parameter, but the AbstractTomcatManagerDeployer always uses this class with update=false.
Do you see a reason to prevent the user from updating a previously deployed war?
Thanks for your time and consideration,
Amnon Khen
amnon.is <at> gmail <dot> com
> Fix redeploy method for Tomcat container to perform actual undeploy and deploy instead of reload
> ------------------------------------------------------------------------------------------------
>
> Key: CARGO-419
> URL:
http://jira.codehaus.org/browse/CARGO-419> Project: Cargo
> Issue Type: Bug
> Components: Tomcat
> Affects Versions: 0.8
> Reporter: Juri Artamonov
> Assignee: Vincent Massol
> Fix For: 0.9
>
> Attachments: patch.txt, redeploy.patch
>
>
> Update redeploy method for Tomcat container to perform actual undeploy and deploy instead of reload.
> Current redeploy method contains call for reload method of Tomcat Manager instead of performing undeploying and deploying deployable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
