Hi Chuck, Once again appreciate your response.
What I did was I created a WAR file and dropped it under the tomcat webapps folder and started it. This helped in overcoming my problem. This process created conf/Catalina/[host]/[appName].xml and copied all the property from my local META-INF/context.xml into the new [appName].xml. This helped the tomcat in reading all the environment variables. Thank you everyone who replied to my mail. Please keep up the good work. Thanks Raj From: "Caldarale, Charles R" <chuck.caldar...@unisys.com> To: Tomcat Users List <users@tomcat.apache.org> Date: 10/27/2011 05:55 PM Subject: RE: context.xml not being read > From: Rajkumar Singh [mailto:rajkumar.si...@digitas.com] > Subject: Re: context.xml not being read > If the context.xml file is being ignored then why the variable that I have > defined in the server.xml is not being read? Should I delete the > META-INF/context.xml file completely? Having a <Context> element in server.xml is strongly discouraged these days. Better to keep it in META-INF/context.xml of the webapp, or in conf/Catalina/[host]/[appName].xml. Regardless, you must have it in only one place; having it in multiple places means the behavior is undefined. Note that if you want to define the default webapp, it should be named ROOT (case sensitive). You must not use path attribute when the <Context> element is in META-INF/context.xml or in conf/Catalina/[host]/[appName].xml. Read the docs on the <Context> element for more details. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org ------------------------------------------------------------------------ Disclaimer The information in this email and any attachments may contain proprietary and confidential information that is intended for the addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, retention or use of the contents of this information is prohibited. When addressed to our clients or vendors, any information contained in this e-mail or any attachments is subject to the terms and conditions in any governing contract. If you have received this e-mail in error, please immediately contact the sender and delete the e-mail.
