geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <>
Subject Re: How to updated config.list during offline deployment
Date Thu, 04 Nov 2004 20:07:10 GMT
	What I am proposing is the equivalent of using the current deploy 
tool, and then adding the module's configId to the server command line 
next time you start it -- which is what you can do today.  I don't see how 
that makes the situation worse.

	You seem to be sugesting that the deploy tool should only work
fully when the server is running, and if the server is not running, then
you need to use a different command to start the server and deploy at the
same time.  Is that right?


On Thu, 4 Nov 2004, Jeremy Boynes wrote:
> You mean, you hope that it starts - you would have to look at the server 
> to see if it actually did. So this has the same "copy-and-pray" utility 
> as dumping the module in a directory.
> I think either you would be checking as you watched the server start 
> (the --add option) or you would test by pinging the server once it had 
> started. The latter option here is exactly as hard as just calling "start"
> My issue is the ambiguity in the outcome of what you propose.

View raw message