RE: contextAdmin question
Title: RE: contextAdmin question Ok. I need to create a war-file? But that can't be all. I must somehow tell tomcat to read that war-file also. How/where do I do that? (Ok, this answer could probably be found in a doc somewhere, but I'm quite lazy.. ;). // Erik -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Sent: Tuesday, May 08, 2001 2:22 AMTo: [EMAIL PROTECTED]Subject: RE: contextAdmin question if a war file is in the webapps directory, the context will be build upon starting tomcat automatically, assuming the AutoStart interceptor has been disabled. The context section in server.xml is to hardcode certain parameters such as reloadable, crosscontext etc. the war gets expanded into a dir of the same name upon startup as the context gets initiated at startup. -Original Message- From: Pavan Seth [mailto:[EMAIL PROTECTED]] Sent: Monday, May 07, 2001 7:37 PM To: [EMAIL PROTECTED] Subject: Re: contextAdmin question You mean to say that..if i create a new one like below.. Context path="/admin" docBase="webapps/admin" crossContext="true" debug="0" reloadable="true" trusted="false" /Context it is not persistent? It disappears after restart/restop? --- [EMAIL PROTECTED] wrote: That was a really good question, and not knowing the answer, I copied my server.xml file, renamed one of the copies, and started tomcat. Added new contexts, shut down tomcat, and compared the two files. Apparently the answer* to your question is "yes, you will have to manually code new contexts into your server.xml file if you want them (contexts, that is) to persist between start/stops of tomcat." * == This answer derived on a Win98 box running Tomcat 3.2.1. YMMV. So my follow-up question is: does anyone know if this is the intended functionality of the contextAdmin tool? And beyond that: where can I find more information about requested, recommended, planned, and existing Tomcat administration tools/servlets. Anyone? Anyone?Here's another question regarding the contextAdmin application that comes with Tomcat. Is it possible to save the new context created to server.xml in any way so that it will exists when I restart tomcat, or do I have to write this code myself? __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
contextAdmin question
Here's another question regarding the contextAdmin application that comes with Tomcat. Is it possible to save the new context created to server.xml in any way so that it will exists when I restart tomcat, or do I have to write this code myself? // Erik
Re: contextAdmin question
You mean to say that..if i create a new one like below.. Context path=/admin docBase=webapps/admin crossContext=true debug=0 reloadable=true trusted=false /Context it is not persistent? It disappears after restart/restop? --- [EMAIL PROTECTED] wrote: That was a really good question, and not knowing the answer, I copied my server.xml file, renamed one of the copies, and started tomcat. Added new contexts, shut down tomcat, and compared the two files. Apparently the answer* to your question is yes, you will have to manually code new contexts into your server.xml file if you want them (contexts, that is) to persist between start/stops of tomcat. * == This answer derived on a Win98 box running Tomcat 3.2.1. YMMV. So my follow-up question is: does anyone know if this is the intended functionality of the contextAdmin tool? And beyond that: where can I find more information about requested, recommended, planned, and existing Tomcat administration tools/servlets. Anyone? Anyone? Here's another question regarding the contextAdmin application that comes with Tomcat. Is it possible to save the new context created to server.xml in any way so that it will exists when I restart tomcat, or do I have to write this code myself? __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
RE: contextAdmin question
Title: RE: contextAdmin question if a war file is in the webapps directory, the context will be build upon starting tomcat automatically, assuming the AutoStart interceptor has been disabled. The context section in server.xml is to hardcode certain parameters such as reloadable, crosscontext etc. the war gets expanded into a dir of the same name upon startup as the context gets initiated at startup. -Original Message- From: Pavan Seth [mailto:[EMAIL PROTECTED]] Sent: Monday, May 07, 2001 7:37 PM To: [EMAIL PROTECTED] Subject: Re: contextAdmin question You mean to say that..if i create a new one like below.. Context path=/admin docBase=webapps/admin crossContext=true debug=0 reloadable=true trusted=false /Context it is not persistent? It disappears after restart/restop? --- [EMAIL PROTECTED] wrote: That was a really good question, and not knowing the answer, I copied my server.xml file, renamed one of the copies, and started tomcat. Added new contexts, shut down tomcat, and compared the two files. Apparently the answer* to your question is yes, you will have to manually code new contexts into your server.xml file if you want them (contexts, that is) to persist between start/stops of tomcat. * == This answer derived on a Win98 box running Tomcat 3.2.1. YMMV. So my follow-up question is: does anyone know if this is the intended functionality of the contextAdmin tool? And beyond that: where can I find more information about requested, recommended, planned, and existing Tomcat administration tools/servlets. Anyone? Anyone? Here's another question regarding the contextAdmin application that comes with Tomcat. Is it possible to save the new context created to server.xml in any way so that it will exists when I restart tomcat, or do I have to write this code myself? __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
RE: contextAdmin question
I believe it will already exist when you use the builtin ContextAdmin app.HTH. :^) A chain is only as strong as its weakest link. Ricky Y. Artigas Analyst/Programmer Information Technology Division Easycall Communications Phils., Inc. - Easycall Internet - 418 Arayat St., Mandaluyong City 1550, Philippines Personal WAP Site: http://www.buzzed.co.uk/mobile/?rya Company Website: http://www.easycall.com.ph Tel.no: (+632) 5338001 ext.6574 Mobile:(+63) 0917-8951783 Pager: 141-002955 Email: [EMAIL PROTECTED] --- IMPORTANT NOTICE: This message (and any attachment hereto) may contain privileged and/or confidential information specific to EasyCall. If you are not the intended addressee indicated in this message, you may not copy or disseminate this message (or any attachment hereto) to anyone. Instead, please destroy this message (and any attachment hereto), and kindly notify the sender by reply email. Any information in this message (and any attachment thereto) that do not relate to the official business of EasyCall shall be understood as neither given nor endorsed by the company. -Original Message- From: Erik Hellman [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, May 08, 2001 1:00 AM To: Tomcat-User@Jakarta. Apache. Org Subject: contextAdmin question Here's another question regarding the contextAdmin application that comes with Tomcat. Is it possible to save the new context created to server.xml in any way so that it will exists when I restart tomcat, or do I have to write this code myself? // Erik
Re: contextAdmin question
It won't disappear if you manually code it into the server.xml file, but as I found out, Tomcat 3.2.1 apparently doesn't write out the new context to the server.xml file if you create the new context using the contextAdmin page. You mean to say that..if i create a new one like below.. Context path="/admin" docBase="webapps/admin" crossContext="true" debug="0" reloadable="true" trusted="false" /Context it is not persistent? It disappears after restart/restop?
