[jira] [Updated] (LOG4J2-2275) ExtendedLogger API should expose trace entry/exit with FQCN

["Raman Gupta (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raman Gupta updated LOG4J2-2275:
--------------------------------
    Description: 
The ExtendedLogger interface does not currently have a way to call trace entry/exit with a FQCN value.

This means that logger wrappers cannot set their FQCN when calling these methods, making correct location-aware logging for trace entry/exit impossible for wrappers.

This was discovered during implementation of the log4j2 Kotlin API in [LOG42-1705|https://issues.apache.org/jira/browse/LOG4J2-1705].

cc: [~jvz]

  was:
The ExtendedLogger interface does not currently have a way to call trace entry/exit with a FQCN value.

This means that logger wrappers cannot set their FQCN when calling these methods, making correct location-aware logging for trace entry/exit impossible for wrappers.

This was discovered during implementation of the log4j2 Kotlin API in LOG42-1705.

cc: [~jvz]


> ExtendedLogger API should expose trace entry/exit with FQCN
> -----------------------------------------------------------
>
>                 Key: LOG4J2-2275
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2275
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 2.10.0
>            Reporter: Raman Gupta
>            Priority: Major
>
> The ExtendedLogger interface does not currently have a way to call trace entry/exit with a FQCN value.
> This means that logger wrappers cannot set their FQCN when calling these methods, making correct location-aware logging for trace entry/exit impossible for wrappers.
> This was discovered during implementation of the log4j2 Kotlin API in [LOG42-1705|https://issues.apache.org/jira/browse/LOG4J2-1705].
> cc: [~jvz]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)