DO NOT REPLY [Bug 17972] New: - Admin webapp should save info to auto-deployed webapp xml files when appropriate

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

Admin webapp should save info to auto-deployed webapp xml files when appropriate

           Summary: Admin webapp should save info to auto-deployed webapp
                    xml files when appropriate
           Product: Tomcat 4
           Version: 4.1.18
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Webapps:Administration
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: Richard.June@hp.com


When webapps are auto-deployed by placing an xml file with their
Context element into the appBase directory, and then the admin
webapp is used to commit changes of any kind, the Context elements
for the auto-deployed webapps are written into the server.xml
file.  From this point on, the xml files placed in the appBase
directory are ignored, and the server.xml file becomes the
only source of deployment information for those webapps.

It would be better if committing changes through the admin
server saved information back to the place it came from,
either:

1) To the server.xml file if the object was originally
   created from an element in that file.
or

2) To the appropriate xml file in the appBase directory
   if the object was created from an element in that
   file.

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