On Thu, 4 Nov 2004, Jeremy Boynes wrote:
> No, you were proposing having the deployment tool hack the internal file
> used by a specific GBean. I object to that as it relies on
> implementation detail.
Hmm. Obviously we're not on the same page here.
So you would be totally comf
Aaron Mulder wrote:
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.
No, you were proposing having
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 d
Aaron Mulder wrote:
If you "deploy" to a server that's not running, then the module
will be started next time the server starts. If you "distribute" to a
server that's not running, then the module will not be started next time
the server starts.
You mean, you hope that it starts - you would h
On Thu, 4 Nov 2004, Jeremy Boynes wrote:
> Pardon me for being dumb but how can you start a module if the server is
> down?
>
> I think we may be trying to hard to kludge 88-style operations into a
> mode that 88 was not intended to support.
If you "deploy" to a server that's not runnin
Aaron Mulder wrote:
I'm working on the new deployer not the old one. As per the
"proposed deployer syntax" message, this one actually offers a JSR-88
start method while the server is not running, which equates to updating
the config list to include the module. I'd rather not start the server to
Actually, it will be
java -jar bin/deployer.jar deploy [module] [plan]
As per the proposed deployer syntax thread. (Though I currently
have a separate new-deployer.jar until we feel comfortable axing the old
one).
Aaron
On Thu, 4 Nov 2004, Dain Sundstrom wrote:
> So I would hav
I'm working on the new deployer not the old one. As per the
"proposed deployer syntax" message, this one actually offers a JSR-88
start method while the server is not running, which equates to updating
the config list to include the module. I'd rather not start the server to
do that...
On Nov 4, 2004, at 11:18 AM, Jeremy Boynes wrote:
Aaron Mulder wrote:
I'd like to be able to add entries to config.list when the server is
not running and I'm doing a deployment. The problem is, the
configuration list GBean isn't running -- it's not in the minimal set
started by the deployer.
Aaron Mulder wrote:
I'd like to be able to add entries to config.list when the server
is not running and I'm doing a deployment. The problem is, the
configuration list GBean isn't running -- it's not in the minimal set
started by the deployer. And even if it was, it would install a shutdown
On Nov 4, 2004, at 10:39 AM, Aaron Mulder wrote:
I'd like to be able to add entries to config.list when the server
is not running and I'm doing a deployment. The problem is, the
configuration list GBean isn't running -- it's not in the minimal set
started by the deployer. And even if it was, it
I'd like to be able to add entries to config.list when the server
is not running and I'm doing a deployment. The problem is, the
configuration list GBean isn't running -- it's not in the minimal set
started by the deployer. And even if it was, it would install a shutdown
hook that bas
12 matches
Mail list logo