Bug 910675 - wrong value of "runtime-name" property for unmanaged deployments
Summary: wrong value of "runtime-name" property for unmanaged deployments
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER2
: EAP 6.1.1
Assignee: Heiko Braun
QA Contact:
URL:
Whiteboard:
Depends On: 920491
Blocks: 975403
TreeView+ depends on / blocked
 
Reported: 2013-02-13 09:00 UTC by Jakub Cechacek
Modified: 2015-02-01 23:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-16 20:30:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-6516 0 Major Resolved Wrong value of "runtime-name" property for unmanaged deployments 2014-08-18 01:37:56 UTC

Description Jakub Cechacek 2013-02-13 09:00:10 UTC
When creating an Unmanaged deployment the value from "Name" field is being used for both "name" and "runtime-name" properties. 

Steps to reproduce:

1. Runtime - Server - Manage Deployments
2. click the add button 
3. in popup window click the "Unmanaged" tab
4. fill in the form
5. click the next button (finish the procedure) 

Path: "/path/is/not/important"
Relative To: ""
Is Archive: true
Name: "name"
Runtime Name: "runtime-name"

Result: This is how created Resource Node looks like in cli

$ /deployment=name/:read-resource
{
    "outcome" => "success",
    "result" => {
        "content" => [{
            "path" => "/path/is/not/important",
            "archive" => true
        }],
        "enabled" => false,
        "name" => "name",
        "persistent" => true,
        "runtime-name" => "name",
        "subdeployment" => undefined,
        "subsystem" => undefined
    }
}

Comment 1 Heiko Braun 2013-02-22 13:20:22 UTC
https://issues.jboss.org/browse/AS7-6516

Comment 2 Jakub Cechacek 2013-03-07 09:17:08 UTC
AFAIK there is no new build of console in ER2 -- moving this back to assigned 

@Heiko: as this is already fixed, I suppose you can change it to modified again.

Comment 3 Jakub Cechacek 2013-04-16 07:21:39 UTC
Verified 6.1.0.ER4

Comment 4 Jakub Cechacek 2013-04-16 07:28:49 UTC
Just ignore the previous comment, It's not verified. I was ahead of myself and I had forgotten to test it in domain.

The issue persists in domain mode - name is still being used also as runtime-name.

Comment 5 Jakub Cechacek 2013-07-03 11:03:44 UTC
Verified 6.1.1.ER2

Comment 6 Scott Mumford 2013-08-12 02:17:40 UTC
Requesting some information for the release note about what was causing this issue and how it was resolved. 

The fix happened somewhere between comment 4 and comment 5, however there's no information I can see about what changed.

Comment 7 Scott Mumford 2013-08-26 00:48:36 UTC
Setting for exclusion from 6.1.1 Release notes and removing NEEDINFO request.


Note You need to log in before you can comment on or make changes to this bug.