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 } }
https://issues.jboss.org/browse/AS7-6516
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.
Verified 6.1.0.ER4
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.
Verified 6.1.1.ER2
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.
Setting for exclusion from 6.1.1 Release notes and removing NEEDINFO request.