[jboss-jira] [JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment
ted won (JIRA)
issues at jboss.org
Fri May 20 11:08:00 EDT 2016
ted won created WFLY-6633:
-----------------------------
Summary: Failed CLI batch command with "deploy --force" for replace deployment
Key: WFLY-6633
URL: https://issues.jboss.org/browse/WFLY-6633
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 10.0.0.Final
Reporter: ted won
Assignee: ted won
Priority: Minor
Fix For: 10.1.0.Final
Attachments: jboss-ejb-in-ear.ear
Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part."
However, it's working in CLI interactive mode without error.
There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below.
Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle()
-------------------------------------------------------------------------------------------
* First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd()
{code}
{
"operation" => "add",
"address" => {"deployment" => "jboss-ejb-in-ear.ear"},
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
* Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace()
{code}
{
"operation" => "full-replace-deployment",
"name" => "jboss-ejb-in-ear.ear",
"address" => [],
"enabled" => true,
"content" => [{"bytes" => bytes {
...
}}]
}
{code}
-------------------------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list