Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 91181 invoked from network); 7 Feb 2007 15:19:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2007 15:19:08 -0000 Received: (qmail 62090 invoked by uid 500); 7 Feb 2007 15:19:11 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 62065 invoked by uid 500); 7 Feb 2007 15:19:11 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 62054 invoked by uid 99); 7 Feb 2007 15:19:11 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Feb 2007 07:19:11 -0800 X-ASF-Spam-Status: No, hits=3.5 required=10.0 tests=FROM_HAS_MIXED_NUMS,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of c1vamsi1c@gmail.com designates 64.233.162.236 as permitted sender) Received: from [64.233.162.236] (HELO nz-out-0506.google.com) (64.233.162.236) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Feb 2007 07:19:02 -0800 Received: by nz-out-0506.google.com with SMTP id j2so242885nzf for ; Wed, 07 Feb 2007 07:18:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=PGy3CxFZIsOCbntTXQNZTm92HURExn0HMxE5yUKAdHJESurE6uKfaeqpQgM8pixT8Udb0D5Ljy39McgWjTJTDqI+eLrDA6K/O5y/nmclluVYinzcjw/YFYA9M27H19uE20esiJCgaGc5SyCDGn3cgr/MOsyaFpzj/gFo/wlVc2A= Received: by 10.114.204.3 with SMTP id b3mr1899353wag.1170861520991; Wed, 07 Feb 2007 07:18:40 -0800 (PST) Received: by 10.114.74.3 with HTTP; Wed, 7 Feb 2007 07:18:40 -0800 (PST) Message-ID: <22d56c4d0702070718j3fedcecfy8a371a9eaedbfb23@mail.gmail.com> Date: Wed, 7 Feb 2007 20:48:40 +0530 From: "Vamsavardhana Reddy" To: user@geronimo.apache.org Subject: Re: Hot Deployment in Geronimo In-Reply-To: <8a855ce00702070707i29f8a1ddma60cf7b0630acff3@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2136_19078586.1170861520963" References: <8a855ce00702070707i29f8a1ddma60cf7b0630acff3@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2136_19078586.1170861520963 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I have noticed this difference in behaviour between G1.0 and G1.1, but never bothered to ask. I never tested if the replaced JSP would be used after restarting the app (or the server). I guess this has something to do with the JSP precompilation. Vamsi On 2/7/07, Hari Krishna Korrapati wrote: > > Hi, > We are using geronimo1.1.1 application server. > After deploying the application, if particular file has been changed, then > we will replace the corresponding file in repository with the latest file > and restart the application. > > In geronimo1.0 whenever we changed some JSP file, we never restarted the > application. We just replaced JSP in repository, and the application worked > fine without restarting the application. But in geronimo1.1.1, JSP's are > not being replaced without restarting the server. > Is it mandatory in geronimo1.1.1 to restart the application after changing > the JSP's in the repository. If not, whats the best way to update the file? > > Is there any property need to be set in config file of geronimo...? > > Could somebody please advice on the same issue. > > > -- > Regards, > Hari ------=_Part_2136_19078586.1170861520963 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I have noticed this difference in behaviour between G1.0 and G1.1, but never bothered to ask.  I never tested if the replaced JSP would be used after restarting the app (or the server).  I guess this has something to do with the JSP precompilation.

Vamsi

On 2/7/07, Hari Krishna Korrapati <harikrishna.korrapati@gmail.com> wrote:
Hi,
       We are using geronimo1.1.1 application server.
After deploying the application, if particular file has been changed, then we will replace the corresponding file in repository with the latest file and restart the application.

In geronimo1.0 whenever we changed some JSP file, we never restarted the application. We just replaced JSP in repository, and the application worked fine without restarting the application. But in geronimo1.1.1, JSP's are not being replaced without restarting the server.
Is it mandatory in geronimo1.1.1 to restart the application after changing the JSP's in the repository. If not, whats the best way to update the file?

Is there any property need to be set in config file of geronimo...?

Could somebody please advice on the same issue.


--
Regards,
Hari

------=_Part_2136_19078586.1170861520963--