<div dir="ltr">I don't think this is really practical, is once we remove the remoting port from the config it means that the CLI will not connect to new servers unless you explicitly specify the port. This has its own backward compatibility problems, as now your scripts will break if you have upgraded you cluster to WF8. <div>
<br></div><div>Also it is possible to set the default protocol in jboss-cli.xml, if your scripts do break because of this change it is basically a one line fix.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Jul 10, 2013 at 1:22 AM, Darran Lofthouse <span dir="ltr"><<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello all,<br>
<br>
I am currently working on the following issue: -<br>
<br>
<a href="https://issues.jboss.org/browse/WFLY-1664" target="_blank">https://issues.jboss.org/browse/WFLY-1664</a><br>
<br>
Recent changes to the CLI mean that it is assuming unless told otherwise<br>
that a HTTP Upgrade is going to be used when connecting to the server,<br>
this means that command already used in scripts to connect to servers<br>
are going to fail unless the scheme is included in the URI.<br>
<br>
I chatted with David to see if there were any options to auto detect<br>
this and fall back to pure Remoting if the remote side of the connection<br>
is pure Remoting - however of the two options available they were both<br>
fairly hacky or unreliable.<br>
<br>
So the alternative is to drop the CLI back to assuming a pure Remoting<br>
connection unless told otherwise.<br>
- Calling connect or starting with -c will still use http-remoting<br>
against the local server as that is defined in the jboss-cli.xml<br>
- Calling connect or --controller with a host and port will assume<br>
connecting directly to remoting.<br>
- Users wanting HTTP upgrade to other servers will need to specify<br>
http-remoting or https-remoting as the scheme when specifying the remote<br>
address.<br>
<br>
One other idea that I have had for the CLI if end users do want the<br>
parameter to the connect command to be as short as possible is to add<br>
multiple host aliases to the jboss-cli.xml - that way the protocol host<br>
and port can be specified in the config and the alias passed to the<br>
connect command. Additionally this would allow us to place different<br>
SSL configuration against each host but.<br>
<br>
Regards,<br>
Darran Lofthouse.<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br></div>