[jboss-jira] [JBoss JIRA] (WFLY-2061) CLI fails to show app status when runtime-name is different from the deployment name

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Fri Sep 13 03:16:04 EDT 2013


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

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

Jay SenSharma <jsenshar at redhat.com> made a comment on [bug 1007696|https://bugzilla.redhat.com/show_bug.cgi?id=1007696]

- According to the "runtime-name" description the users should be allowed to choose a different runtime-name for their deployments.

- "description" =>  "Name by which the deployment should be known within a server's runtime. This would be equivalent to the file name of a deployment file, and would form the basis for such things as default Java Enterprise Edition application and module names. This would typically be the same as 'name', but in some cases users may wish to have two deployments with the same 'runtime-name' (e.g. two versions of \"foo.war\") both available in the deployment content repository, in which case the deployments would need to have distinct 'name' values but would have the same 'runtime-name'."
                
> CLI fails to show app status when runtime-name is different from the deployment name
> ------------------------------------------------------------------------------------
>
>                 Key: WFLY-2061
>                 URL: https://issues.jboss.org/browse/WFLY-2061
>             Project: WildFly
>          Issue Type: Bug
>          Components: CLI, Server
>    Affects Versions: 8.0.0.Alpha4
>         Environment: All
>            Reporter: Jay Kumar SenSharma
>            Assignee: Jason Greene
>
> If an application is deployed with a different "runtime-name" other than the actual EAR "name" then CLI fails to show the Status of the application.

--
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