[
https://issues.jboss.org/browse/WFCORE-152?page=com.atlassian.jira.plugin...
]
James Perkins updated WFCORE-152:
---------------------------------
Description:
I'm not setting a target for this as likely part of this needs to be solved in the
logmanager. Currently rewriting properties does not unset properties that have been
removed from the property map. It seems simple enough to just pass a {{null}} value to the
property and then remove the property, but this won't work for primitives.
From the WildFly perspective there is no way from the configuration
API to determine the type for a property to set. This is the part that should probably be
handled in the logmanager. WildFly will need to set the value to {{null}} once this is
solved on the logmanager side.
was:
I'm not setting a target for this as likely part of this needs to be solved in the
logmanager. Currently rewriting properties does not unset properties that have been
removed from the property map. It seems simple enough to just pass a {{null}} value to the
property and then remove the property, but this won't work for primitives.
From the WildFly perspective there is know way from the configuration
API to determine the type for a property to set. This is the part that should probably be
handled in the logmanager. WildFly will need to set the value to {{null}} once this is
solved on the logmanager side.
Rewriting the property attribute on custom handlers or formatters
does not unset values
---------------------------------------------------------------------------------------
Key: WFCORE-152
URL:
https://issues.jboss.org/browse/WFCORE-152
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
I'm not setting a target for this as likely part of this needs to be solved in the
logmanager. Currently rewriting properties does not unset properties that have been
removed from the property map. It seems simple enough to just pass a {{null}} value to the
property and then remove the property, but this won't work for primitives.
From the WildFly perspective there is no way from the configuration API to determine the
type for a property to set. This is the part that should probably be handled in the
logmanager. WildFly will need to set the value to {{null}} once this is solved on the
logmanager side.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)