Logging framework about protobuf-rpc-pro

[GoogleCodeExporter]

I fully understand your point. i've used ACL for many many years in libraries, 
but when it comes to choosing a logging framework at container level i used to 
use log4j - but due to the arrival of SLF4j in several open source libraries, 
its not possible to use log4j on container level and get the SLF4j logging into 
it nicely. The consequence is that the container needs to use SLF4j and 
configure it so all logging frameworks log over SLF4j.



<dependency>
                        <groupId>org.slf4j</groupId>
                        <artifactId>jcl-over-slf4j</artifactId>
                        <version>1.6.1</version>
                    </dependency>
                    <dependency>
                        <groupId>org.slf4j</groupId>
                        <artifactId>log4j-over-slf4j</artifactId>
                        <version>1.6.1</version>
                    </dependency>
                    <dependency>
                        <groupId>org.slf4j</groupId>
                        <artifactId>jul-to-slf4j</artifactId>
                        <version>1.6.1</version>
                    </dependency>
                    <dependency>
                        <groupId>ch.qos.logback</groupId>
                        <artifactId>logback-classic</artifactId>
                        <version>0.9.26</version>
                    </dependency>



 ( Personaly i dont know why we need yet another simple logging framework - considering i havent seen anything in SLF4j that you can't do in log4j or whatever )

I will investigate whether to change to direct SLF4j logging in the next 
release....with your other functional requests...:)

Original comment by [email protected] on 5 Jul 2012 at 9:34

• Changed state: Accepted

[GoogleCodeExporter]

It looks like even netty has had this issue discussed:
https://netty.io/Blog/To+use+SLF4J+or+not%2C+that+is+the+question

they have their own internal logging layer - where it makes even sense for them 
to migrate to slf4j instead of modifying their own logger to use slf4j 
internally. So i finally moved with the log4j-migrator util to slf4j native.

Original comment by [email protected] on 2 Jan 2013 at 2:23

• Changed state: Fixed