geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik B. Craig" <>
Subject Re: Questions about using Gshell on a remote server instance
Date Thu, 21 Feb 2008 18:33:53 GMT

I'm not sure how it's *supposed* to be by design, but my expectations  
would be the same as yours - it would shutdown the the instance that  
you are remotely connected to and not the local instance. As such, I  
agree that it may confuse users.
Perhaps this behavior should be changed?

Erik B. Craig

On Feb 21, 2008, at 12:16 PM, Jason Warner wrote:

> I was working with gshell in trunk and noticed something that I  
> thought was odd.  I had used deploy/connect to connect to a remote  
> instance of geronimo.  I then went to issue a geronimo/stop-server  
> command but I didn't provide the hostname or port for the remote  
> server.  The command attempted to shutdown a local instance of  
> geronimo.  I was confused as to why this would be the case.  My  
> expectation would be that if I were connected to a remote instance,  
> then any commands sent to a geronimo server would be directed at  
> that instance.  I think this behavior might confuse users.  Is there  
> a reason things are working the way they currently are?  Is it  
> technically feasible to accomplish this with the way the command is  
> written or is it just not worth the effort?  I'd like to see what  
> other think about this, but I'm definitely going to document it in  
> the wiki.
> Thanks,
> -- 
> ~Jason Warner

View raw message