RE: Tomcat 5 and Context Descriptors
Hi, If you use context .xml files, you can put them in $CATALINA_HOME/conf/[engine name]/[host name] or in the META-INF directory of the WAR file representing your webapp. If you're just deploying webapps without a context XML file, you can put them in the host's appBase. Then you don't need any XML file for your context. But you can't just put context XML files in the host's appBase. Yoav Shapira Millennium Research Informatics -Original Message- From: John H [mailto:[EMAIL PROTECTED] Sent: Monday, April 12, 2004 2:42 PM To: [EMAIL PROTECTED] Subject: Tomcat 5 and Context Descriptors Good afternoon, We are currently looking at upgrading our Tomcat 4.1.24 installation to 5.0.19. I've installed a test environment to see what sort of migration issues there will be, and so far I've only encountered one. Under 4.1.24, we have a Host entry in server.xml that looks like this: Host name=localhost appBase=C:\localwebapps\conf unpackWARs=true autoDeploy=true deployXML=true ... /Host This allowed us to place context descriptors in C:\localwebapps\conf (XML files with individual Context tags, one file for each Context), and these contexts would be loaded at startup. With 5.0.19, I modified the Host entry to look like this: Host name=localhost appBase=C:\localwebapps\conf unpackWARs=true autoDeploy=true deployXML=true deployOnStartup=true ... /Host However, the context descriptors in C:\localwebapps\conf are not loaded at startup, and I can't seem to figure out how to load them at all. The only way to load them is to place them in $CATALINA_HOME/conf/[enginename]/[hostname]/ I'm assuming I'm missing something, since I doubt that Tomcat 5 would force you to use $CATALINA_HOME/conf/[enginename]/[hostname]/ for context descriptors. Looking through the Deployment HOWTO, the Context Descriptors heading has this blurb: A Context XML descriptor is a fragment of XML data which contains a valid Context element which would normally be found in the main server configuration file (conf/server.xml), and allows easy and automated manipulation of web applications by the various management tools available in Tomcat. For a given host, the Context descriptors are located in $CATALINA_HOME/conf/[enginename]/[hostname]/foo.xml. Note that while the name of the file is not tied to the webapp name, Tomcat will create Context descriptors which match the webapp name whenever it will generate a Context descriptor. This seems to indicate that I have to use $CATALINA_HOME/conf/[enginename]/[hostname]/. However, the very next heading, 'Deploying Tomcat on Startup', has this to say: The webapps which are present in the host appBase will be deployed if the host deployOnStartup property is true. The deployment process is the following: a.. The Context XML declarations will be deployed first b.. ... This seems to indicate that I should be able to do what I want to do. Any ideas? John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5 and Context Descriptors
Is this something new in TC5? Context XML's in appBase worked in 4.1.24. - Original Message - From: Shapira, Yoav [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Monday, April 12, 2004 2:42 PM Subject: RE: Tomcat 5 and Context Descriptors Hi, If you use context .xml files, you can put them in $CATALINA_HOME/conf/[engine name]/[host name] or in the META-INF directory of the WAR file representing your webapp. If you're just deploying webapps without a context XML file, you can put them in the host's appBase. Then you don't need any XML file for your context. But you can't just put context XML files in the host's appBase. Yoav Shapira Millennium Research Informatics -Original Message- From: John H [mailto:[EMAIL PROTECTED] Sent: Monday, April 12, 2004 2:42 PM To: [EMAIL PROTECTED] Subject: Tomcat 5 and Context Descriptors Good afternoon, We are currently looking at upgrading our Tomcat 4.1.24 installation to 5.0.19. I've installed a test environment to see what sort of migration issues there will be, and so far I've only encountered one. Under 4.1.24, we have a Host entry in server.xml that looks like this: Host name=localhost appBase=C:\localwebapps\conf unpackWARs=true autoDeploy=true deployXML=true ... /Host This allowed us to place context descriptors in C:\localwebapps\conf (XML files with individual Context tags, one file for each Context), and these contexts would be loaded at startup. With 5.0.19, I modified the Host entry to look like this: Host name=localhost appBase=C:\localwebapps\conf unpackWARs=true autoDeploy=true deployXML=true deployOnStartup=true ... /Host However, the context descriptors in C:\localwebapps\conf are not loaded at startup, and I can't seem to figure out how to load them at all. The only way to load them is to place them in $CATALINA_HOME/conf/[enginename]/[hostname]/ I'm assuming I'm missing something, since I doubt that Tomcat 5 would force you to use $CATALINA_HOME/conf/[enginename]/[hostname]/ for context descriptors. Looking through the Deployment HOWTO, the Context Descriptors heading has this blurb: A Context XML descriptor is a fragment of XML data which contains a valid Context element which would normally be found in the main server configuration file (conf/server.xml), and allows easy and automated manipulation of web applications by the various management tools available in Tomcat. For a given host, the Context descriptors are located in $CATALINA_HOME/conf/[enginename]/[hostname]/foo.xml. Note that while the name of the file is not tied to the webapp name, Tomcat will create Context descriptors which match the webapp name whenever it will generate a Context descriptor. This seems to indicate that I have to use $CATALINA_HOME/conf/[enginename]/[hostname]/. However, the very next heading, 'Deploying Tomcat on Startup', has this to say: The webapps which are present in the host appBase will be deployed if the host deployOnStartup property is true. The deployment process is the following: a.. The Context XML declarations will be deployed first b.. ... This seems to indicate that I should be able to do what I want to do. Any ideas? John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5 and Context Descriptors
Hi, Is this something new in TC5? Context XML's in appBase worked in 4.1.24. Yup, the move from appBase to conf/[engine name]/[host name] is a change in TC5. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
