Bug 48662 - context.xml expansion on deployment improvements
context.xml expansion on deployment improvements
Status: RESOLVED FIXED
Product: Tomcat 7
Classification: Unclassified
Component: Catalina
trunk
PC Mac OS X 10.4
: P2 enhancement (vote)
: ---
Assigned To: Tomcat Developers Mailing List
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2010-02-02 22:44 UTC by Mark Thomas
Modified: 2011-04-13 14:22 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Thomas 2010-02-02 22:44:07 UTC
Two parts:

1. Log a warning/info message if Tomcat ignores a bundled context.xml in favour of one in CATALINA_BASE/<engine name>/<host name>

2. Make the extraction/copying of context.xml configurable, probably via a new attribute extractXml on the host
Comment 1 Mark Thomas 2010-02-02 22:44:44 UTC
Mark as enhancement
Comment 2 Mark Thomas 2010-03-28 11:57:59 UTC
This has been implemented for 7.0.x and will be included in 7.0.0 onwards
Comment 3 Tim Astle 2011-04-13 14:22:07 UTC
What was the reason behind this change?  Is there a security reason or something else?  I would have assumed the default value for copyXML would have been true and not false to have people moving from Tomcat 6 to 7 have their systems continue to function the same way.

I read the details about this change and there isn't any back story.
http://tomcat.apache.org/tomcat-7.0-doc/config/host.html
http://tomcat.apache.org/migration.html#6.0.x_to_7.0.x