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@localhost:9990 /] deploy helloworld-rs.war
[standalone@localhost:9990 /] deploy helloworld-rs-second.war —disabled
[standalone@localhost:9990 /] :replace-deployment(name=helloworld-rs-second.war,to-replace=helloworld-rs.war,runtime-name=foo.war)
[standalone@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" =>

}
}

Foo.war is not applied. Looks like it was ignored.