DO NOT REPLY [Bug 9960] New: - Deploy issue with local Context

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9960>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9960

Deploy issue with local Context

           Summary: Deploy issue with local Context
           Product: Tomcat 4
           Version: 4.1.4
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: peterj@liberate.com


If a webapp is not present when Tomcat is started, but a local file
webapps/MyApp.xml exists, the <Context> in the xml file will be added to
server.xml when MyApp is deployed.  Although the <Context> is added to
server.xml, the deploy fails, reporting "Application already exists at path
/MyApp"--in other words, the configuration for the application is present but
the app itself isn't.  (The parameters not listed in MyApp.xml that may exist in
web.xml are also not added, but this may be simply because MyApp.war is not
being accepted.)

In order to get MyApp.war file onto the server, it's necessary to undeploy the
webapp, which removes the <Context> from server.xml, and deploy it again...
except the new deployment ignores the <Context> in MyApp.xml and uses only the
defaults in the webapp's web.xml file.

This appears to be a Catch-22 situation: either you have the local configuration
and no app, or the app and no local configuration.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>