[jboss-jira] [JBoss JIRA] (WFLY-1972) CLI command should not allow same runtime-name to be used at another deploy

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Wed Sep 18 09:22:03 EDT 2013


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

RH Bugzilla Integration commented on WFLY-1972:
-----------------------------------------------

Petr Kremensky <pkremens at redhat.com> made a comment on [bug 983980|https://bugzilla.redhat.com/show_bug.cgi?id=983980]

Verified in EAP 6.2.0.ER2.

EAP is now acting as described in comment 2

If user tries to deploy application with already used runtime name:
"There is already a deployment called ${name} with the same runtime name ${runtime-name} on server group ${server-group}"
message is shown.
                
> CLI command should not allow same runtime-name to be used at another deploy
> ---------------------------------------------------------------------------
>
>                 Key: WFLY-1972
>                 URL: https://issues.jboss.org/browse/WFLY-1972
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Emmanuel Hugonnet
>            Assignee: Brian Stansberry
>
> Having two deployments with the same runtime-name in the domain content repository, so they can be deployed to different instances, is ok.
> Having two deployments with the same runtime name actually deployed to an instance is not (that's the issue here).
> Same for standalone.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list