On Jul 11, 2007, at 12:42 PM, Andrew La Motte-Mitchell wrote:
Hello,
I'm a new poster, and I apologize if this e-mail is off-topic in
any way. I tried searching online for reviews that would give me
insight about this question, but didn't find much. I appreciate
your help!
I am an intern who has been put in charge of designing a new logger
for my company, and log4cxx looks great. Unfortunately, it doesn't
meet all of our (very specific) needs so we would have to extend
it. I'm hoping to get feedback from users who have tried to extend
it. Was the code documented sufficiently well? (I've found great
use documentation, but had trouble finding any design documentation
that would help developers... this is probably my fault, so if I'm
just looking in the wrong place let me know :)
There is very little log4cxx-specific design documentation as log4cxx
is strongly patterned after log4j. The vast majority of log4j
extensions could be pretty easily transliterated to log4cxx.
On a related note, can anyone comment on the reliability of this
library? My bosses won't commit to anything they don't believe is
rock-solid, so if you think it is (or you don't) please let me know.
There are many appenders and in general the more obscure appenders
are going to be less tested and more likely to have issues or work at
all. However, there are a decent number of reports of using log4cxx
in production systems (search the lists for production and you should
get some hits).
