[
https://issues.apache.org/jira/browse/LOG4J2-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220412#comment-15220412
]
Zbynek Vyskovsky commented on LOG4J2-1336:
------------------------------------------
Matt, not sure I understand completely, but the issue with the original
implementation is that it provides different interface that is different from
the one in log4j 1.2. I'm not looking for another interface/class which would
serve the same.
Anyway, I tried it and it fixes the problem. And I'm happy about the name, I
had hard times coming up with proper one :-) Thanks.
> LoggerFactory in 1.2 API module is not compatible with 1.2
> ----------------------------------------------------------
>
> Key: LOG4J2-1336
> URL: https://issues.apache.org/jira/browse/LOG4J2-1336
> Project: Log4j 2
> Issue Type: Bug
> Components: log4j 1.2 emulation
> Affects Versions: 2.5
> Reporter: Zbynek Vyskovsky
> Labels: patch
> Fix For: 2.6
>
> Attachments: log4j-1.2-compatible-factory.diff
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> LoggerFactory from log4j 1.2 compatibility layer is not compatible with the
> original 1.2 version. Therefore software which creates its customized loggers
> is failing due to AbstractMethodError error.
> The fix is quite simple - just keep the original interface. The attached
> patch continues to support the current method too, but uses different
> interface name for the functionality so it doesn't clash with 1.2 API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
