[jboss-jira] [JBoss JIRA] (WFCORE-4603) Replace Deployment --runtime-name option not working

[Brian Stansberry (Jira)]

    [ https://issues.jboss.org/browse/WFCORE-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770871#comment-13770871 ] 

Brian Stansberry edited comment on WFCORE-4603 at 8/14/19 12:12 PM:
--------------------------------------------------------------------

[~ehugonnet] [~yersan] -A tangent to clean up as part of any work on this:

https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/org/jboss/as/server/deployment/DeploymentReplaceHandler.java#L84

That should be context.readResource(PathAddress.EMPTY_ADDRESS, false); as we don't want to read the entire model just to check for child names.-

Never mind; I missed that there was already a PR for this.


was (Author: brian.stansberry):
[~ehugonnet] [~yersan] A tangent to clean up as part of any work on this:

https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/org/jboss/as/server/deployment/DeploymentReplaceHandler.java#L84

That should be context.readResource(PathAddress.EMPTY_ADDRESS, false); as we don't want to read the entire model just to check for child names.

> Replace Deployment --runtime-name option not working
> ----------------------------------------------------
>
>                 Key: WFCORE-4603
>                 URL: https://issues.jboss.org/browse/WFCORE-4603
>             Project: WildFly Core
>          Issue Type: Bug
>    Affects Versions: 10.0.0.Beta4
>         Environment: Red Hat JBoss Enterprise Application Platform (EAP) 7.2 CP 3.
>            Reporter: Emmanuel Hugonnet
>            Assignee: Emmanuel Hugonnet
>            Priority: Major
>
> The scenario is that, if you have a deployment to be switched by a new one, the runtime-name property doesn't work the way it should. See the sequence of the commands bellow:
> [standalone at localhost:9990 /] deploy helloworld-rs.war
> [standalone at localhost:9990 /] deploy helloworld-rs-second.war —disabled
> [standalone at localhost:9990 /] :replace-deployment(name=helloworld-rs-second.war,to-replace=helloworld-rs.war,runtime-name=foo.war) 
> [standalone at localhost:9990 /] /deployment=helloworld-rs-second.war:read-resource
> {
>     "outcome" => "success",
>     "result" => {
>         "content" => [{"hash" => bytes {
>             0xfe, 0x24, 0x1f, 0xd3, 0x19, 0xa3, 0x72, 0xd4,
>             0xc6, 0xa4, 0x48, 0xe7, 0x8b, 0x9c, 0xc1, 0xd4,
>             0xc7, 0x17, 0xdf, 0xaa
>         }}],
>         "enabled" => false,
>         "name" => "helloworld-rs-second.war",
>         "owner" => undefined,
>         "persistent" => true,
>         "runtime-name" => "helloworld-rs-second.war",
>         "subdeployment" => undefined,
>         "subsystem" => {
>             "undertow" => undefined,
>             "ejb3" => undefined,
>             "logging" => undefined
>         }
>     }
> }
> Foo.war is not applied. Looks like it was ignored.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)