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@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
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev



--
---
Nik
_______________________________________________ jboss-as7-dev mailing list jboss-as7-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev