[
https://issues.jboss.org/browse/ELY-744?page=com.atlassian.jira.plugin.sy...
]
Darran Lofthouse commented on ELY-744:
--------------------------------------
+1 I think we need to ensure the parent category remains unchanged but will be good to use
more fine grained categories where we have made a decision to call out the mech name.
Overall ideally exciting logging config examples should remain unchanged. That is not
completely set in stone but if we can retain compatibility we can avoid discussions on
compatibility ;-)
Create log categories for mechanisms instead of prefixing messages
------------------------------------------------------------------
Key: ELY-744
URL:
https://issues.jboss.org/browse/ELY-744
Project: WildFly Elytron
Issue Type: Enhancement
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Minor
In log messages are often used prefixes to determine context of the message - typically
name of mechanism:
{code:java}
log.trace("ClientCertAuthenticationMechanism: re-authentication succeed");
{code}
This should be replaced by standalone log categories.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)