Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ammulder@gmail.com designates
 64.233.166.183 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=hoPKp27zxHl/L6WNpKZPS4GiGp2Gt3lqOvC5Td1rqyy0ppEnI4hvVFpFaep/nmsSBvwir8JGRpBlk+8TC51IJLM6YRJKQxPeIyxqYj9mdoUnitCfVBnYEhcJ/oTMaMwaBkoipSda+6BGqhCsSUO1cu9bMiPl46qcDwOMQuUUW00=
Message-ID: <74e15baa0605032211g61c781f7v81f442432d447e92@mail.gmail.com>
Date: Thu, 4 May 2006 01:11:11 -0400
From: "Aaron Mulder" <ammulder@alumni.princeton.edu>
Sender: ammulder@gmail.com
To: dev@geronimo.apache.org
Subject: Re: hot deployment directory
In-Reply-To: <e98662b90605032202y439530bap7ee20d2cd8a01a2b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <e98662b90605032145u7852c5beuc0f78a03e4f4966e@mail.gmail.com>
	 <74e15baa0605032149te19f66ehac7bc3f38c672163@mail.gmail.com>
	 <e98662b90605032202y439530bap7ee20d2cd8a01a2b@mail.gmail.com>

Please do any work in the 1.1 branch.  Right now 1.2 is in a very
uncertain state.  Though, I suspect the issues will be different in
1.1, so you may want to start by testing the same things there.

IIRC, the hot deployer does not yet check the timestamp of the
deployments in it its directory during startup and compare those to
the timestamps of the current modules to determine whether an existing
file there is the same as ever or a new version was copied in while
the server was down.  That should be doable in 1.1.

Thanks,
    Aaron

On 5/4/06, Rakesh Ranjan <rakesh.geronimo@gmail.com> wrote:
> Thanks Aaron for the quick response.
>  Here are two issues with Geronimo-1.2-SNAPSHOT which need to be fixed :
>  1. When Geronimo starts, it try to deploy the modules in the hot deploym=
ent
> directory even if that module is already deployed. Since the  application=
 is
> already deployed, it throws an error : the application already exists in =
the
> server.
>
>  2. Geronimo is not able to deploy the database plans kept in the hot
> deployment directory.
>
>  Rakesh Ranjan
>
>
> On 5/4/06, Aaron Mulder <ammulder@alumni.princeton.edu> wrote:
> > You're welcome to look at that.  Can you list the issues you're going
> > to attempt to fix?  There seems to be a lot of variation in what
> > people think the problems actually are.
> >
> > Thanks,
> >     Aaron
> >
> > On 5/4/06, Rakesh Ranjan < rakesh.geronimo@gmail.com> wrote:
> > > Hi all,
> > >
> > >  I have not seen much activity in hot deployment directory enhancemen=
t.
> I
> > > have seen there are some bugs in the current implementation of hot
> > > deployment directory. I am interested to work on this enhancement. So=
 i
> want
> > > to know the current status of this enhancement? Is some other member
> working
> > > on this issue?
> > >
> > >  Rakesh
> > >
> >
>
>