10:47 p.m.
Isn't it the same as "quit" which is already available? Or do you mean
something else?
By the way, from what I remember of the early design discussions, the
CLI doesn't maintain a connection with the management server. Each CLI
operation/command connects to be server. So the CLI is really
"disconnected" from the server.
-Jaikiran
On Wednesday 02 November 2011 09:05 AM, Vimal Kansal wrote:
I wonder if that is on the agenda?
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
10:58 p.m.
I *love* the disconnected aspect, but it can get confused if you swap out the domain-mode
server on port 9990 with a standalone on 9990. The CLI does maintain some state regarding
the type of API it's "connected" to.
Not that that's a very common or useful use-case, but...
-Bob
On Nov 1, 2011, at 11:47 PM, Jaikiran Pai wrote:
Isn't it the same as "quit" which is already available?
Or do you mean
something else?
By the way, from what I remember of the early design discussions, the
CLI doesn't maintain a connection with the management server. Each CLI
operation/command connects to be server. So the CLI is really
"disconnected" from the server.
-Jaikiran
On Wednesday 02 November 2011 09:05 AM, Vimal Kansal wrote:
> I wonder if that is on the agenda?
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
11 p.m.
Actually when you execute "quit", you come out of jboss-admin and are on
shell prompt.
On 2/11/2011 2:47 PM, Jaikiran Pai wrote:
Isn't it the same as "quit" which is already available?
Or do you mean
something else?
By the way, from what I remember of the early design discussions, the
CLI doesn't maintain a connection with the management server. Each CLI
operation/command connects to be server. So the CLI is really
"disconnected" from the server.
-Jaikiran
On Wednesday 02 November 2011 09:05 AM, Vimal Kansal wrote:
> I wonder if that is on the agenda?
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
6:13 a.m.
On 2 Nov 2011, at 03:47, Jaikiran Pai wrote:
Isn't it the same as "quit" which is already available?
Or do you mean
something else?
By the way, from what I remember of the early design discussions, the
CLI doesn't maintain a connection with the management server. Each CLI
operation/command connects to be server. So the CLI is really
"disconnected" from the server.
Yes, this is why starting and stopping
the AS while for example testing, but leaving CLI in the 'connected' state works
-Jaikiran
On Wednesday 02 November 2011 09:05 AM, Vimal Kansal wrote:
> I wonder if that is on the agenda?
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
1:47 a.m.
Having 'connect' it sounds like a logical addition. But what would be a
use-case?
If you need to re-connect to another controller you can execute
'connect' again with the corresponding arguments. It'll disconnect and
connect to the new controller.
On 11/02/2011 04:35 AM, Vimal Kansal wrote:
I wonder if that is on the agenda?
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
2:01 a.m.
Perhaps a usecase would be for running cross-server scripts?
batch start
connect to server1
do stuff
disconnect
connect to server2
do stuff
batch run
On Wed, Nov 2, 2011 at 8:47 AM, Alexey Loubyansky <
alexey.loubyansky(a)redhat.com> wrote:
Having 'connect' it sounds like a logical addition. But what
would be a
use-case?
If you need to re-connect to another controller you can execute
'connect' again with the corresponding arguments. It'll disconnect and
connect to the new controller.
On 11/02/2011 04:35 AM, Vimal Kansal wrote:
> I wonder if that is on the agenda?
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
---
Nik
2:13 a.m.
Yup, that is precisely the use case I had in mind but then I realise
'disconnect' is not required as when I issue the second connect, I am
assuming, I get disconnected from frist. Correct me please if I am wrong.
On 2/11/2011 6:01 PM, Nicklas Karlsson wrote:
Perhaps a usecase would be for running cross-server scripts?
batch start
connect to server1
do stuff
disconnect
connect to server2
do stuff
batch run
On Wed, Nov 2, 2011 at 8:47 AM, Alexey Loubyansky
<alexey.loubyansky(a)redhat.com <mailto:alexey.loubyansky@redhat.com>>
wrote:
Having 'connect' it sounds like a logical addition. But what would
be a
use-case?
If you need to re-connect to another controller you can execute
'connect' again with the corresponding arguments. It'll disconnect and
connect to the new controller.
On 11/02/2011 04:35 AM, Vimal Kansal wrote:
> I wonder if that is on the agenda?
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
---
Nik
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4:09 a.m.
As I wrote, 'connect' will disconnect first if connected before
connecting to the new controller.
On 11/02/2011 08:01 AM, Nicklas Karlsson wrote:
Perhaps a usecase would be for running cross-server scripts?
batch start
connect to server1
do stuff
disconnect
connect to server2
do stuff
batch run
On Wed, Nov 2, 2011 at 8:47 AM, Alexey Loubyansky
<alexey.loubyansky(a)redhat.com <mailto:alexey.loubyansky@redhat.com>> wrote:
Having 'connect' it sounds like a logical addition. But what would be a
use-case?
If you need to re-connect to another controller you can execute
'connect' again with the corresponding arguments. It'll disconnect and
connect to the new controller.
On 11/02/2011 04:35 AM, Vimal Kansal wrote:
> I wonder if that is on the agenda?
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
---
Nik
4:25 a.m.
Yup that is clear now.
Thx
Vimal
On 2/11/2011 8:09 PM, Alexey Loubyansky wrote:
As I wrote, 'connect' will disconnect first if connected
before
connecting to the new controller.
On 11/02/2011 08:01 AM, Nicklas Karlsson wrote:
> Perhaps a usecase would be for running cross-server scripts?
>
> batch start
> connect to server1
> do stuff
> disconnect
> connect to server2
> do stuff
> batch run
>
> On Wed, Nov 2, 2011 at 8:47 AM, Alexey Loubyansky
> <alexey.loubyansky@redhat.com<mailto:alexey.loubyansky@redhat.com>>
wrote:
>
> Having 'connect' it sounds like a logical addition. But what would be a
> use-case?
>
> If you need to re-connect to another controller you can execute
> 'connect' again with the corresponding arguments. It'll disconnect
and
> connect to the new controller.
>
> On 11/02/2011 04:35 AM, Vimal Kansal wrote:
> > I wonder if that is on the agenda?
> >
> > _______________________________________________
> > jboss-as7-dev mailing list
> >
jboss-as7-dev@lists.jboss.org<mailto:jboss-as7-dev@lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev@lists.jboss.org<mailto:jboss-as7-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
>
>
> --
> ---
> Nik
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4800
days inactive
4800
days old
9 comments
6 participants
participants (6)
-
Alexey Loubyansky -
Bob McWhirter -
Jaikiran Pai -
Kabir Khan -
Nicklas Karlsson -
Vimal Kansal