[wildfly-dev] Change CLI to Default to Remoting

Brian Stansberry brian.stansberry at redhat.com
Tue Jul 9 11:57:58 EDT 2013


On 7/9/13 10:22 AM, Darran Lofthouse wrote:
> Hello all,
>
> I am currently working on the following issue: -
>
>     https://issues.jboss.org/browse/WFLY-1664
>
> Recent changes to the CLI mean that it is assuming unless told otherwise
> that a HTTP Upgrade is going to be used when connecting to the server,
> this means that command already used in scripts to connect to servers
> are going to fail unless the scheme is included in the URI.
>
> I chatted with David to see if there were any options to auto detect
> this and fall back to pure Remoting if the remote side of the connection
> is pure Remoting - however of the two options available they were both
> fairly hacky or unreliable.
>
> So the alternative is to drop the CLI back to assuming a pure Remoting
> connection unless told otherwise.
>    - Calling connect or starting with -c will still use http-remoting
> against the local server as that is defined in the jboss-cli.xml
>    - Calling connect or --controller with a host and port will assume
> connecting directly to remoting.
>    - Users wanting HTTP upgrade to other servers will need to specify
> http-remoting or https-remoting as the scheme when specifying the remote
> address.
>

Sounds fine. I'd be fine with a simple heuristic based on the port as 
well, so --controller=localhost:9990 would default to http-remoting.

> One other idea that I have had for the CLI if end users do want the
> parameter to the connect command to be as short as possible is to add
> multiple host aliases to the jboss-cli.xml - that way the protocol host
> and port can be specified in the config and the alias passed to the
> connect command.  Additionally this would allow us to place different
> SSL configuration against each host but.
>

+1.

> Regards,
> Darran Lofthouse.
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat


More information about the wildfly-dev mailing list