Nick,
This problem has been already reported a few days ago. Nevertheless, thank
you for reporting it.
As you observe, nlog4j admits a String instead of an object in its
printing methods.
There is a known method for fixing this problem. You can expect it to be
fixed in a few hours.
At 07:08 AM 8/16/2005, Nick Faiz wrote:
Hi,
We recently added nlog4j-1.2.14 as the logging mechanism for Apache
Directory Server.
I've been developing another library, called Atlassian User, which
includes ApacheDS, and all of its dependencies. I have recently begun to
integrate Atlassian User with another application, which uses log4j-1.2.8 .
When working on the integration within IDEA I encounter
NoSuchMethodError(s) on simple logging statements which *only* use a
String as an argument to the logger (e.g. log.debug("example message" +
exception.getMessage()):
java.lang.NoSuchMethodError:
org.apache.log4j.Logger.debug(Ljava/lang/String;)V
I've looked at the source of nlog4j and log4j and I can see the slight
difference in Category - nlog4j specifies a String, instead of an object,
for methods such as debug(..), info(..), etc..
I've also written a quick test application which uses two classes - one
dependent on log4j and one dependent on nlog4j. A runtime
IncompatibleClassChangeError occurs:
Exception in thread "main" java.lang.IncompatibleClassChangeError
Can you please advise me as to how to overcome this problem? If nlog4j
cannot work alongside log4j libraries then many pre-existing applications
will not be able to use ApacheDS.
Cheers,
Nick
--
ATLASSIAN - http://www.atlassian.com/
Confluence - the enterprise wiki - tried it yet?
http://www.atlassian.com/confluence/
--
_______________________________________________
nlog4j-dev mailing list
[email protected]
http://slf4j.org/mailman/listinfo/nlog4j-dev
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
_______________________________________________
nlog4j-dev mailing list
[email protected]
http://slf4j.org/mailman/listinfo/nlog4j-dev
