Executing a read-attribute operation is allowed on non-existing resources with for attributes with defined read handlers ------------------------------------------------------------------------------------------------------------------------ Key: WFCORE-1800 URL: https://issues.jboss.org/browse/WFCORE-1800 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: James Perkins Assignee: Brian Stansberry Attachments: WFCORE-1800.patch If an attribute defines an {{OperationStepHandler}} the global {{read-attribute}} operation will execute the handler regardless if the resource exists. Here's an example that will successfully execute and return the name {{invalid}} for the {{name}} attribute even though the resource does not exist. {code} /path=invalid(name=name) {code} For attributes that use the default means of reading the attribute value the {{context.readResource(PathAddress.EMPTY_ADDRESS, false)}} is already invoked which will cause a failure. For attributes which define a custom read OSH the outcome is unpredictable as the existence of the resource is not validated before invoking the OSH.