-
Bug
-
Resolution: Done
-
Major
-
None
-
None
When trying to create an xml-formatter or json-formatter with the same name as another resource (e.g. a file-handler), the operation fails:
[standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=aaa.log}) {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=logging/xml-formatter=test:add { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No property \"dateFormat\" setter found for formatter \"test\"", "rolled-back" => true }
Similarly vice-versa, when trying to create another resource in logging subsystem with the same name as an xml-formatter or a json-formatter, the operation fails:
[standalone@localhost:9990 /] /subsystem=logging/json-formatter=test:add {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=test.log}) { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No property \"pattern\" setter found for formatter \"test\"", "rolled-back" => true }
The same scenario works for e.g. pattern-formatter:
[standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=test.log}) {"outcome" => "success"} [standalone@localhost:9990 /] /subsystem=logging/pattern-formatter=test:add {"outcome" => "success"}
- relates to
-
WFCORE-2951 Add JSON formatter resources to the logging subsystem
- Resolved
-
WFCORE-2952 Add an XML formatter resources to the logging subsystem
- Resolved
-
WFCORE-3337 Logging resources shouldn't be allowed to removed if they are in-use
- Resolved