[jboss-jira] [JBoss JIRA] (WFLY-2094) Different results for read-resource operation in WildFly master and EAP 6.x

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFLY-2094:
----------------------------------------

This is because when the management http server was changed to undertow, the logic changed to only send the failure-description. For example,

https://github.com/wildfly/wildfly/commit/e8369c3#L11L327

Likely a simple enough fix.
                
> Different results for read-resource operation in WildFly master and EAP 6.x
> ---------------------------------------------------------------------------
>
>                 Key: WFLY-2094
>                 URL: https://issues.jboss.org/browse/WFLY-2094
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Harald Pehl
>            Assignee: Brian Stansberry
>
> When executing a read-resource operation for a model node that does not exist, I get different results in WildFly master and EAP 6.x:
> {code:title=WildFly master}
> "JBAS014807: Management resource '[
>     (\"core-service\" => \"management\"),
>     (\"access\" => \"authorization\"),
>     (\"role-mapping\" => \"Administrator\")
> ]' not found"
> {code}
> {code:title=EAP 6.1}
> {
>     "outcome" => "failed",
>     "failure-description" => "JBAS014807: Management-Ressource '[
>     (\"core-service\" => \"management\"),
>     (\"access\" => \"authorization\"),
>     (\"role-mapping\" => \"Administrator\")
> ]' nicht gefunden",
>     "rolled-back" => true
> }
> {code}
> In EAP 6.x I get the correct error result which includes {{"outcome" => "failed"}} whereas in WildFly I just receive the error message wihtout the surrounding model node. 
> The error occurs when using the HTTP protocol. Using the CLI / native interface both versions return the correct (complete) error response.

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