Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 23160 invoked from network); 20 Apr 2010 23:27:11 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Apr 2010 23:27:11 -0000 Received: (qmail 8279 invoked by uid 500); 20 Apr 2010 23:27:08 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 8129 invoked by uid 500); 20 Apr 2010 23:27:08 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 8115 invoked by uid 99); 20 Apr 2010 23:27:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Apr 2010 23:27:08 +0000 X-ASF-Spam-Status: No, hits=-0.2 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anandhs@gmail.com designates 209.85.221.183 as permitted sender) Received: from [209.85.221.183] (HELO mail-qy0-f183.google.com) (209.85.221.183) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Apr 2010 23:27:02 +0000 Received: by qyk13 with SMTP id 13so5529088qyk.18 for ; Tue, 20 Apr 2010 16:26:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:received:message-id :subject:from:to:content-type; bh=wWe6cbKwVocCl7wClxDV7rqa9xaeKpfgI5rVYPeR/UI=; b=qX926KEONQ5qAokSpKf4vgpSxD0WfMPsxx9gHsZXv+33V/yWNoByJwkgWxW7maJNXG IxVJ00Epk6hLPN8GLgI9SYGWf7W4Ol8EXB65lIfc2GUAWTZaVpJuaUQgQfZB17Axqrda jhB8ilAOtIuhLpa3P2JsQ/3EEfGpdbuJNSVNo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ixRXAXCGE3raaI7jwba5IsuCfs8LOzl8YOppGoD4JIqLSiYmzXRgfLeWkzbSUkqEbZ d0ywpE+8FVo7jMnYtBKB1dLuVaGiZa6qTU7bisuR+A1UV6sSmc6y1bLo4/hqtjRQG3R6 +hVEK4bSvnPbuZQZ3ZJOWPeHV60TE7bksVeMU= MIME-Version: 1.0 Received: by 10.229.218.149 with HTTP; Tue, 20 Apr 2010 16:26:40 -0700 (PDT) Date: Tue, 20 Apr 2010 16:26:40 -0700 Received: by 10.229.224.133 with SMTP id io5mr6959103qcb.37.1271806000467; Tue, 20 Apr 2010 16:26:40 -0700 (PDT) Message-ID: Subject: Installing auto updates for my webapp hosted on Tomcat From: Anand HS To: Tomcat Users List Content-Type: multipart/alternative; boundary=0016363b8510e1916b0484b368a1 --0016363b8510e1916b0484b368a1 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a webapplication deployed in tomcat and have been asked to develop an auto updater that can grab a new update and apply the updates to my webapp. I want to ask the community to see if there are 'hooks' tomcat provides to achieve this. In essence here is what Im expecting to achieve - 1. A simple agent ( can be a java program inside my web app itself ) senses there is an update. 2. when an update is available, it stops the tomcat server. 3. Applies the update ( similar to redeploy along with configuration file changes ) . 4. restarts the tomcat. Some of the ideas Im after are - 1. Deploy my updater agent outside of tomcat and hence it can stop and start the tomcat servers. 2. Have the updater agent as part of my webapp itself and with the help of Tomcat API ( ? ) , restart the application. I need advice from the community on other approaches as well as any support tomcat provides out of the box. Thanks, Anand --0016363b8510e1916b0484b368a1--