[ https://issues.jboss.org/browse/WFLY-6633?page=com.atlassian.jira.plugin.... ] ted won updated WFLY-6633: -------------------------- Description: Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part." {code} batch deploy --force ./jboss-ejb-in-ear.ear run-batch {code} 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} ------------------------------------------------------------------------------------------- was: 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)