[
https://issues.jboss.org/browse/WFCORE-3891?page=com.atlassian.jira.plugi...
]
Michal Petrov commented on WFCORE-3891:
---------------------------------------
[~jamezp], I've been looking into this issue. The one case not mentioned here is that
if you set up formatters named A and B then you can create handler A and give it
named-formatter B (and give A to B) but you cannot give formatter A to handler A.
Seems like the thing to do would be to tweak the logmanager. Since the default formatter
can only be assigned to one handler there's no reason to store it with the other
manually created formatters and that way there would be no need to check for naming
collisions, unless I'm missing something.
Cannot create xml-formatter and json-formatter with the same name as
existing resources in logging subsystem
------------------------------------------------------------------------------------------------------------
Key: WFCORE-3891
URL:
https://issues.jboss.org/browse/WFCORE-3891
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: Nikoleta Žiaková
Assignee: James Perkins
Priority: Major
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:
{code}
[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
}
{code}
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:
{code}
[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
}
{code}
The same scenario works for e.g. {{pattern-formatter}}:
{code}
[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"}
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)