-
Bug
-
Resolution: Done
-
Minor
-
7.1.0.DR7
-
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.
- is cloned by
-
WFCORE-2300 ReadResourceNameOperationStepHandler does not check if the resource exists before returning the resource name
- Resolved
- is incorporated by
-
JBEAP-8294 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta2
- Closed
-
JBEAP-8874 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta6
- Closed