-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
Trying to read the category attribute on a nonexistent logger results in success:
[standalone@localhost:9990 /] /subsystem=logging/logger=aaaaaa:read-attribute(name=category) { "outcome" => "success", "result" => "aaaaaa" }
Any other attributes can't be read and the operation correctly fails, e.g.:
[standalone@localhost:9990 /] /subsystem=logging/logger=aaaaaab:read-attribute(name=level { "outcome" => "failed", "failure-description" => "WFLYCTL0216: Management resource '[ (\"subsystem\" => \"logging\"), (\"logger\" => \"aaaaaab\") ]' not found", "rolled-back" => true }
This behavior is confusing, the operation should fail for any attribute on a nonexistent logger.
- clones
-
JBEAP-7063 ReadResourceNameOperationStepHandler does not check if the resource exists before returning the resource name
- Closed