Valery Sorokin created JBCOMMON-133: --------------------------------------- Summary: 'https-remoting' not mentioned in 'connect --help' output Key: JBCOMMON-133 URL: https://issues.jboss.org/browse/JBCOMMON-133 Project: JBoss Common Issue Type: Bug Environment: installed EAP7, domain/secured mode Reporter: Valery Sorokin Assignee: Dimitris Andreadis Priority: Minor in this help output not mentioned option 'https-remoting', which actually exists and works ---------------------------------------------------------------------------- [disconnected /] connect --help SYNOPSIS connect [host][ort] DESCRIPTION Connects to the controller on the specified host and port using the specified protocol. The default values can be customized by specifying the desired defaults as command line arguments when launching the CLI. E.g. jboss-cli.sh controller=http-remoting://controller-host.net:1234 Or jboss-cli.sh controller=controller-host.net In this case, the default port will be 9990 and the default protocol will be http. Note, specifying controller argument will only set the default host and port values for the connect command but will not automatically connect to the specified controller. To connect automatically after the launch, use '--connect' switch. E.g. jboss-cli.sh --connect jboss-cli.sh --connect controller=controller-host.net jboss-cli.sh --connect controller=controller-host.net:1234 jboss-cli.sh --connect controller=remote://controller-host.net:1234 jboss-cli.sh --connect controller=http-remoting://controller-host.net:1234 The host may be any of these formats: - a host name, e.g. localhost - an IPv4 address, e.g. 127.0.0.1 - an IPv6 address, e.g. [::1] ARGUMENTS protocol - optional, default value is http. host - optional, default value is localhost. port - optional, default value is 9990. ---------------------------------------------------------------------------- -- This message was sent by Atlassian JIRA (v6.4.11#64026)