Ok, I found out what can happen when just using
"indexOf" - when the logger class appears two
times in a row the logged method again is wrong
(the one of the second entry).
I am already using a cusom layout class and now
work around that problem by using a customized
location information class that looks up the
method and logger class directly from the throwable
stacktrace ...
/Markus
Antwort auf Markus Rechtien <[EMAIL PROTECTED]>:
Hi,
Im trying to use log4j with proxy classes and had the problem
that I got the wrong method name within logging output when
a classname exists more than one time within the stacktrace
of the location information of the logging event.
I took a look inside the code and found out, that the loggerclass
is looked up with lastIndexOf within the string of the stacktrace.
off course this is the reason why wrong method names appear
in the logging output.
Is there a reason why indexOf (first index of) cant be used to look
up the logger class in the stacktrace ?
Many thanks and all the best,
Markus
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--
[address]
Markus Rechtien
Rheiner Landstr. 83
D-49078 Osnabrück
[email]
[EMAIL PROTECTED]
[phone]
+49 (0)541 3347736
[cellular]
+49 (0)176 22254427
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
