Bug 983980

Description of problem:
If an application is deployed via JBoss CLI utility as following:

deploy /home/jsenshar/myapp.war --runtime-name=abc.war --name=myapp1

Then the context root of the application becomes "/abc" (As runtime name is being treated as Context-Root so even if the app name is myapp.war, Still the context root will be /abc which is good)

However when another application is attempted to be deployed on the same JBoss with the same "runtime-name" still JBoss CLI/JBoss Container does not throw any error as the "/abc" context is already registered with the same name.

Example:
deploy /home/jsenshar/myapp.war --runtime-name=abc.war --name=myapp2

So second time when abc.war is being deployed with different "name" (however the "runtime-name" is same as pervious) then JBoss/CLI should throw error Rather than uploading the Applciation content in the "data/content" directory.



Version-Release number of selected component (if applicable):


How reproducible:
Step-1).
======== Deploy "myapp.war" as following:
[standalone@localhost:9999 /] deploy /home/jsenshar/myapp.war --runtime-name=abc.war --name=myapp1


The JBoss console/log output will be as following:

18:01:25,995 INFO  [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /NotBackedUp/Intern_Training/jboss-eap-6.1/standalone/data/content/eb/66cce417ab2bd456e0530deae361abb05f97ec/content
18:01:25,998 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "myapp1" (runtime-name: "abc.war")
18:01:26,054 INFO  [org.jboss.web] (ServerService Thread Pool -- 64) JBAS018210: Register web context: /abc
18:01:26,173 INFO  [org.jboss.as.server] (management-handler-thread - 1) JBAS018559: Deployed "myapp1" (runtime-name : "abc.war")


Step-2).
======== Modify the "myapp.war" and then deploy it again on the same JBoss with a different "--name" (keep the "--runtime-name" same) as following:
[standalone@localhost:9999 /] deploy /home/jsenshar/myapp.war --runtime-name=abc.war --name=myapp2

Now check the JBoss Console/log, you will notice that JBoss is uploading the content of the application in "data/content" directory.   So here it is expected that JBoss should complaint/throwError that an application with the same "runtime-name" is already registered. 

18:04:14,428 INFO  [org.jboss.as.repository] (management-handler-thread - 6) JBAS014900: Content added at location /NotBackedUp/Intern_Training/jboss-eap-6.1/standalone/data/content/16/df3dd071683f6c188e69e64dd885acc82fab61/content




Actual results:
See Steps to reproduce.


Expected results:

JBoss should wither throw Error when another deployment attempt is made with the same "runtime-name" rather than allowing to upload the new application's content in the "data/content" directory.

Additional info:
$JBOSS_HOME/docs/schema/jboss-as-config_1_3.xsd which states the runtime-name should be unique among the same server group.  

++++++++++++++
        <xs:attribute name="runtime-name" use="required">
            <xs:annotation>
                <xs:documentation>Name by which the deployment will be known within a running server.of the deployment.
                    Does not need to be unique across all deployments in the domain, although it must be unique within
                    an individual server. For example, two different deployments running on different servers in
                    the domain could both have a 'runtime-name' of 'example.war', with one having a 'name'
                    of 'example.war_v1' and another with an 'name' of 'example.war_v2'.
                </xs:documentation>
            </xs:annotation>
        </xs:attribute>
++++++++++++++