[jboss-jira] [JBoss JIRA] (WFLY-6633) Failed CLI batch command with "deploy --force" for replace deployment

[ted won (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ted won updated WFLY-6633:
--------------------------
    Steps to Reproduce: 
1. %WILDFLY_HOME/bin/domain.sh

2. vi deploy.cli
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch

3. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch executed successfully

4. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.

5. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.

  was:
1. %WILDFLY_HOME/bin/domain.sh

2. vi deploy.cli
batch
deploy --force ./jboss-ejb-in-ear.ear
run-batch

3. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch executed successfully
4. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.
5. jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=tedwon --password=xxx --file="deploy.cli"
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part.



> 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
>              Labels: cli, jboss
>             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)