ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: [Contribution] EJB Hot deployment task
Date Mon, 25 Mar 2002 05:29:47 GMT
On 2002.03.25 00:07:33 -0500 Erik Hatcher wrote:
> ----- Original Message -----
> From: "David Jencks" <>
> > I haven't exactly been following this closely but I guess I'll take the
> > bait...
> >
> > JBoss users have always had an ant-based deploy tool in copy (==deploy)
> and
> > delete(==undeploy).  What advantage is there to wrapping these up in an
> add
> > on to some other task? Or is there some reason you'd want to call the
> > deployer through a jmx connector?
> How about remote server deployment though?  Does JBoss have this
> capability?
> (probably a silly question - I suspect it does).
>     Erik

Right now you can deploy specific urls located anywhere, however there is
no url scanner, just a directory scanner.  There is a farm service letting
you deploy explicitly on one machine and have the deployment replicated
over the whole farm.

OK, first I took the bait...

>From a more well rounded viewpoint, it would be useful to be able to call
the MainDeployer mbean from ant:

-- you can deploy lots of files remotely without telling the scanner about
them explicitly.

-- you can deploy packages in a specified order

-- you can avoid the delay of waiting for the scanner to notice the

In general, it would be nice to have a jmx caller task in ant-- you could
use it for controlling just about anything in jboss.

Maybe I'll take this opportunity to once again push the idea that ant
should be a bunch of mbeans running in a jmx mbean server.

So  I guess jonas will beat jboss at this, since I have to be out of town
next week;-) (unless someone else takes this on)

david jencks
> --
> To unsubscribe, e-mail:   <>
> For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message