Our company has adopted log4j and quite frankly, love it. I've only gotten positive
feedback for making the decision to migrate to log4j. We have been using it as
designed, for logging/tracing and performance has not been an issue since there are
virtually no log records being written in a pro
We have an several custom implementations of a resource bundler resolver
that meets requirements for different customers. Basically is works
like the ResourceBundle.getBundle(String baseName, Locale locale) except
that our implementation takes two extra parameters that have to do with
customer sp
Ray,
It is a shame that Jonas does not provide an application classloader
property like some of the other app servers we use. That would
definitely take care of the problem.
I wrapped log4j 1.2 beta so it looks like I may have to backtrack and
rewrite my log4j extensions and wrapper to use the
Ceki,
We posted the symptom last Friday on the Jonas forum but no one seems to
have run into the problem at this point. I will post the "changes
between log4j..." you included to the Jonas group and see what kind of
response I get and let you know.
Thanks for the reply,
Bill
-Original Mess
We downloaded the latest version of Jonas 2.4.4 that uses log4j v1.0.4
set of API's.
We are using the log4j 1.2 beta exclusively and when I put the log4j 1.2
beta jar file in front of the class path, Jonas throws a
java.lang.NoSuchMethodError at
org.objectweb.monolog.wrapper.log4j.MonologCategory
