[jboss-jira] [JBoss JIRA] (WFLY-7558) Replacing a deployment (which uses a different runtime name), starts using the filename as runtime-name

[Fake Lastname (JIRA)]

Fake Lastname created WFLY-7558:
-----------------------------------

             Summary: Replacing a deployment (which uses a different runtime name), starts using the filename as runtime-name
                 Key: WFLY-7558
                 URL: https://issues.jboss.org/browse/WFLY-7558
             Project: WildFly
          Issue Type: Bug
          Components: Server, Web Console
    Affects Versions: 10.1.0.Final
         Environment: OS X client, wildfly domain is running on CentOS 7
            Reporter: Fake Lastname
            Assignee: Jason Greene


This is a two step problem.  If an ear has been uploaded and configured to use a different runtime name that works and the domain uses the correct runtime name.

If I replace the ear it doesn't have an input box to choose a new runtime name- yet it defaults the new runtime name to the filename that's being used to replace the deployment.

I tried to workaround this by renaming my ear to the runtime name and using that to replace the existing deployment but that gives this exception:

Cannot upload deployment: {"domain-failure-description" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"otherName.ear\")]' not found"}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)