Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 85099 invoked from network); 3 Apr 2003 16:55:44 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 3 Apr 2003 16:55:44 -0000 Received: (qmail 26476 invoked by uid 97); 3 Apr 2003 16:57:35 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 26468 invoked from network); 3 Apr 2003 16:57:35 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 3 Apr 2003 16:57:35 -0000 Received: (qmail 83621 invoked by uid 500); 3 Apr 2003 16:55:27 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 83610 invoked from network); 3 Apr 2003 16:55:27 -0000 Received: from unknown (HELO mail.cdi-hq.com) (207.104.45.33) by daedalus.apache.org with SMTP; 3 Apr 2003 16:55:27 -0000 Received: from PIP (192-168-11-102.cdi-hq.com [192.168.11.102]) by mail.cdi-hq.com (8.10.1/8.10.1) with ESMTP id h33GtTt09118 for ; Thu, 3 Apr 2003 08:55:29 -0800 (PST) From: "mike jackson" To: "'Tomcat Users List'" Subject: RE: Going Live Date: Thu, 3 Apr 2003 08:55:21 -0800 Message-ID: <003001c2fa01$d361d2b0$660ba8c0@north.cdihq.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <000001c2fa00$773a03f0$a9894218@prosperity> Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Personally I've not been happy with the Oracle version of Apache / Java Servlet / JSP server. We run Apache w/Tomcat on all web servers, including those that use Oracle for the backend database. However all that said, I'd look at making a WAR file and deploying it that way. It puts all the files and settings required for the app into one file. The container will extract that and build the file system structures required. There's much less chance for error. --mikej -=----- mike jackson mjackson@cdi-hq.com -----Original Message----- From: Sandra Patricia Hunter [mailto:redbirdofthesouth@shaw.ca] Sent: Thursday, April 03, 2003 8:46 AM To: 'Tomcat Users List' Subject: Going Live Right now I am just working on development on a stand alone (more or less) machine. Eventually my app will be moved to a corporate web server. Is it appropriate to keep Tomcat as my JSP and servlet container? Because we are using Oracle we have in place the Oracle Apache server already. How horrific would it be to move files to it? Are there any considerations I need to be aware of in the move? My intention would be just to copy my files into a new installation of Tomcat with all the relevant paths, etc. Is there a good source of info on this subject that I have overlooked? Sandra Patricia Hunter Systems Development and Web Design --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org