geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Boynes" <>
Subject RE: Review of refactored deployment classes
Date Thu, 16 Oct 2003 05:22:58 GMT
I'd actually classify directory scanning as a legacy of pre-88 days. As 88
becomes commonplace, more and more development tools will use it to push
deployments directly to the target server.

So yes, for now, we need to do something like this but ultimately it would
be turned off for development as well. However, this would not be a
'production mode' (a la WL) but simply a configuration where the scanner
service was not started.


> -----Original Message-----
> From: gianny DAMOUR []
> Sent: Wednesday, October 15, 2003 9:25 PM
> To:
> Subject: Re: Review of refactored deployment classes
> David Jencks wrote:
> >Why are auto-deploy folders needed?  Depending on the tools you
> use, they
> >are sometimes a convenience in development, but can be simply
> annoying with
> >other choices.  For instance, JBoss has a jboss-jmx ant task that can be
> >used to call the jboss deployer with a url.  You can then have a deploy
> >target in your ant script and forget copying your app into the
> hot-deploy
> >directory.  I'm not saying one way is always better than the other, I've
> >used both.
> I agree. I assume that they are needed for development as a
> convenience and
> not recommanded for production deployments.
> Do you plan to support two server modes a la WebLogic? I mean a
> Development
> mode with a "standard" auto-deploy folder and a Production mode
> where this
> feature is switched off.
> I think that this is one of the nicies, which makes a product
> more appealing
> than another, yet this is my 2 cents.
> Cheers,
> Gianny
> _________________________________________________________________
> Hotmail : un compte GRATUIT qui vous suit partout et tout le temps !

View raw message