]
Stan Silvert commented on AS7-785:
----------------------------------
Update. When you specify --runtime-name it works properly. So the problem is with the
help text and also the fact that it did not throw an error when I used the underscore
version "runtime_name"
[standalone@localhost:9999 /] deploy --help
Synopsis: deploy (file_path [--name=deployment_name]
[--runtime_name=deployment_runtime_name] [--force] | --name=deployment_name)
[--server-groups=group_name (,group_n
ame)* | --all-server-groups]
Description: deploys the application designated by the file_path or enables an already
existing
but disabled in the repository deployment designated by the name
argument.
If executed w/o arguments, will list all the existing deployments.
Arguments:
file_path - the path to the application to deploy. Required in case the
deployment
doesn't exist in the repository.
The path can be either absolute or relative to the current
directory.
name - the unique name of the deployment. If the file path argument is
specified
the name argument is optional with the file name been the default
value.
If the file path argument isn't specified then the command is
supposed to
enable an already existing but disabled deployment, and in this
case the
name argument is required.
runtime_name - optional, the runtime name for the deployment.
force - if the deployment with the specified name already exists, by
default,
deploy will be aborted and the corresponding message will
printed.
Switch --force (or -f) will force the replacement of the existing
deployment
with the one specified in the command arguments.
server-groups - comma separated list of server group names the deploy command
should apply to.
Either server-groups or all-server-groups is required in the
domain mode.
This argument is not applicable in the standalone mode.
all-server-groups - indicates that deploy should apply to all the available server
groups.
Either server-groups or all-server-groups is required in domain
mode.
This argument is not applicable in the standalone mode.
l - in case none of the required arguments is specified the command
will
print all of the existing deployments in the repository. The
presence of the -l switch
will make the existing deployments printed one deployment per
line, instead of
Setting runtime-name seems to have no effect
--------------------------------------------
Key: AS7-785
URL:
https://issues.jboss.org/browse/AS7-785
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.0.0.CR1
Reporter: Stan Silvert
Assignee: Alexey Loubyansky
If I upload a deployment using the runtime_name argument, it seems to have no effect.
Also, for consistency with internals, suggest using "runtime-name" for the
argument instead of the underscored "runtime_name".
[standalone@localhost:9999 /] deploy
/as7trunk/as7jsf/mojarra2.0/jsfwithjsp/target/jsfwithjsp.war --runtime_name=jsfjsp
'jsfwithjsp.war' deployed successfully.
[standalone@localhost:9999 /] /deployment=jsfwithjsp.war/:read-resource
{
"outcome" => "success",
"result" => {
"name" => "jsfwithjsp.war",
"runtime-name" => "jsfwithjsp.war",
"content" => [{
"input-stream-index" => 0,
"hash" => bytes {
0xe1, 0xfb, 0xee, 0x1c, 0xed, 0x9e, 0x8e, 0x1e,
0xa0, 0x09, 0xd6, 0x47, 0xc1, 0x44, 0x5d, 0xdb,
0xca, 0x7d, 0xc0, 0x72
}
}],
"enabled" => true
},
"compensating-operation" => undefined
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: