[
https://issues.apache.org/jira/browse/LOG4J2-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980793#comment-13980793
]
Mikael Ståldal commented on LOG4J2-611:
---------------------------------------
Yes, this issue can be closed now.
I have sent my Hazelcast factory to Ralph for review, and I will then try to
contribute it to the Hazelcast project.
However, I think it is important that Log4j 2 does not depend on SLF4J, and
that we strive to get other projects use Log4j 2 directly. SLF4J is problematic
when you try to use it multiple times in the same JVM, such as using it to get
Hazelcast to log via Log4j 2 in a web app, AND also use SLF4J to get Jetty to
log via Log4j 2. It seems like either of them works separately, but not both at
the same time.
I like Log4j 2 since you get an SLF4J like API without all this mess that SLF4J
creates. IMHO, having a generic log wrapper is a broken concept, and SLF4J is
not better than Commons-Logging, it just breaks in a different way.
> Logj 1.2 emulation is not complete
> ----------------------------------
>
> Key: LOG4J2-611
> URL: https://issues.apache.org/jira/browse/LOG4J2-611
> Project: Log4j 2
> Issue Type: Bug
> Components: log4j 1.2 emulation
> Affects Versions: 2.0-rc1
> Reporter: Mikael Ståldal
> Priority: Minor
>
> The class org.apache.log4j.spi.LoggingEvent is empty, which makes Hazelcast
> to fail since it tries to use this constructor:
> {{org.apache.log4j.spi.LoggingEvent.<init>(Ljava/lang/String;Lorg/apache/log4j/Category;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V}}
> It is used here (line 117):
> https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/logging/Log4jFactory.java
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
