https://bz.apache.org/bugzilla/show_bug.cgi?id=57701

Dylan Lexie <dile...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #32741|0                           |1
        is obsolete|                            |
                 CC|                            |dile...@gmail.com

--- Comment #5 from Dylan Lexie <dile...@gmail.com> ---
Created attachment 34076
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=34076&action=edit
Patch to provide "redeploy" functionality in Tomcat Manager

This patch is based on the work of Fernando Boaglio but addresses the issues
raised by Mark Thomas. Removing the context from the host (as in,
host.removeChild) was not sufficient, as the logic invoked by check() deals
with protected/private members of a hostConfig. To complete this functionality,
I saw no better option than to expose a public version of HostConfig.undeploy.

In addition to redeploy support in the HTML manager, this patch adds the
redeploy command to the text manager and a redeploy ant task for the ant-based
text manager wrapper. Maintaining consistency between these closely related
utilities seems to be a more coherent update than just literally fulfilling the
feature request.

Since the issue parameters state Tomcat 8.0, I worked from 8.0.x trunk.
However, I share the OP's wish to see this feature in Tomcat 7. Is there a
"right" way to try to facilitate this? For instance, would it be at all
appropriate to re-mark the issue pertinent to 7 and instead provide a patch
(which might be identical) for that version?

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to