tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32418] - URL is not supported for WAR deployment in Tomcat 5 Manager.
Date Mon, 14 Nov 2005 12:07:31 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32418>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32418


brenmcguire@tariffenet.it changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




------- Additional Comments From brenmcguire@tariffenet.it  2005-11-14 13:07 -------
(In reply to comment #5)
> I don't understand how this is different from using the deploy task, and telling
> it to upload your war (since it does the same: the webapp is transferred to the
> server = no benefit). The only difference is that it was pulled (so you need a
> server of some sort) rather than pushed (the Ant task does the pushing for you).
> 
> If the WAR is local to the server, then the deploy form you're using allows to
> not transfer the webapp, which has a benefit (and is why I left it; otherwise,
> it would be gone too).

The big difference is that the WAR file is already there. While you are
uploading the WAR file, the application must not be there (undeployed) and this
is very significant in time-critical applications.
We currently are building a "updater" web application, that receives (via
uploading) the building blocks of a webapp, then builds the WAR, finally sends
the WAR file path to the caller that, after that, calls /deploy using this path.
This way, the time that the webapp is down is limited to the operation of
unpacking the war and the "real" deployment, thus eliminating the time needed
for upload.
Another thing. If you don't want to add complexity to implement this feature,
why you still report in the documentation?
Best regards
Antonio Petrelli

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message