Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 35043 invoked from network); 13 Jul 2000 15:32:35 -0000 Received: from tau.sinix.net (194.224.112.7) by locus.apache.org with SMTP; 13 Jul 2000 15:32:35 -0000 Received: from info.sni.es ([194.224.112.16]) by tau.sinix.net (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id net for ; Thu, 13 Jul 2000 17:32:32 +0200 Received: from madt009a.siemens.es by info.sni.es via smtpd (for tau.sinix.net [194.224.112.7]) with SMTP; 13 Jul 2000 15:32:37 UT Received: by madt009a.siemens.es with Internet Mail Service (5.5.2650.21) id <334C3NDH>; Thu, 13 Jul 2000 17:33:49 +0100 Message-ID: <15B5A0CA85F4D111814200A0C9B7B629BA42E1@ZARS001A> From: "Ripalda-Marin, Miguel-Angel" To: tomcat-user@jakarta.apache.org Subject: RE: tomcat.conf vs tomcat-apache.conf Date: Thu, 13 Jul 2000 17:33:47 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks a lot Jeffrey, that is the thing I was just thinking about... personally I think that = it makes sense trying to 'automatize' as much as possible the 'deployment process'... and it seems reasonable to me doing that by using the = web.xml files in our .war distribution files to regenerate the server.xml on Tomcat's startup... Once more, thanks for your time and attention... Miguel =C1ngel Ripalda Mar=EDn=20 Siemens Elasa S.A.=20 T, I + D Sistemas=20 Pol. Malpica, D-98 50016 Zaragoza, Espa=F1a * (34) 976 760 300 ext. 405 * (34) 976 760 346 * maripalda@elasa.siemens.es -----Mensaje original----- De: Jeffrey M. Bischoff [mailto:JBischoff@bds.com] Enviado el: jueves 13 de julio de 2000 17:28 Para: 'tomcat-user@jakarta.apache.org' Asunto: RE: tomcat.conf vs tomcat-apache.conf Well I think that they are working on some automatic context detection = for 3.2 which would make server.xml automatically generated with the right contexts for whatever webapps you have deployed (or in .war files which = it will automatically expand even in 3.1). For now though, we do have to manually code the contexts in ourselves :( -Jeff B -----Original Message----- From: Ripalda-Marin, Miguel-Angel [mailto:maripalda@elasa.siemens.es] Sent: Thursday, July 13, 2000 12:27 PM To: tomcat-user@jakarta.apache.org Subject: RE: tomcat.conf vs tomcat-apache.conf So, as you said, Jeffrey I understand that I can deploy my webapps as = .war files. That way I can rely on Tomcat to automaticaly expand all the subdirectory structure for my webapp... but I still have to 'code by = hand' the virtual URI's for my webapp... is it right? Miguel =C1ngel Ripalda Mar=EDn=20 Siemens Elasa S.A.=20 T, I + D Sistemas=20 Pol. Malpica, D-98 50016 Zaragoza, Espa=F1a * (34) 976 760 300 ext. 405 * (34) 976 760 346 * maripalda@elasa.siemens.es -----Mensaje original----- De: Jeffrey M. Bischoff [mailto:JBischoff@bds.com] Enviado el: jueves 13 de julio de 2000 17:20 Para: 'tomcat-user@jakarta.apache.org' Asunto: RE: tomcat.conf vs tomcat-apache.conf As I understand it, the server.xml file is not automatically generated. = It is the main tool for configuring tomcat's overall configuration (at = least if you want to use the automatically generated apache-tomcat.conf) Web.xml = in the conf folder is a place to set default values for anything that you = leave out in the web.xml files for individual projects. I don't know how = things work in 3.2B but that seems to be how they work in 3.1 -Jeff B ( If I'm wrong someone please correct me ) -----Original Message----- From: Ripalda-Marin, Miguel-Angel [mailto:maripalda@elasa.siemens.es] Sent: Thursday, July 13, 2000 12:19 PM To: tomcat-user@jakarta.apache.org Subject: RE: tomcat.conf vs tomcat-apache.conf Ok... but I was just wondering if the contents of server.xml are also automatically generated (may starting from the several web.xml of each webapp deployed to the $TOMCAT_HOME/webapps directory)... Miguel =C1ngel Ripalda Mar=EDn=20 Siemens Elasa S.A.=20 T, I + D Sistemas=20 Pol. Malpica, D-98 50016 Zaragoza, Espa=F1a * (34) 976 760 300 ext. 405 * (34) 976 760 346 * maripalda@elasa.siemens.es -----Mensaje original----- De: Brian Richards [mailto:ncmusic@pobox.com] Enviado el: jueves 13 de julio de 2000 17:10 Para: tomcat-user@jakarta.apache.org Asunto: Re: tomcat.conf vs tomcat-apache.conf yes it is automatically generated from the contents of server.xml. -brian ----- Original Message ----- From: "mike niemaz" To: Sent: Thursday, July 13, 2000 11:00 AM Subject: Re: tomcat.conf vs tomcat-apache.conf > Then Nam Kheong wrote: > > > Let me try to help, just read the difference moments ago... > > > > You use tomcat.conf if you are running tomcat without apache. That = mean, > > tomcat will serve all static pages(.HTML), servlets and JSP pages. > > However, tomcat is very slow and inefficient in serving static = pages, thus > > you need to make apache to serve static pages and tomcat to serve = the > > servlets and .JSP pages. This method will render tomcat as an = add-on to > > apache. > > > > This is where tomcat-apache.conf comes in. > > but tomcat-apache.conf is automatically generated so > it no much use, is it? > > > >