asterisk-java-devel

[Asterisk-java-devel] Suggested changes to JavaLoggingLog

[Johan J. <joh...@ko...>]

Hi,

I noticed a drawback with wrapping the java logging api in the asterisk-java 
Log framework. The class and method names printed out by the java Logger is 
always JavaLoggingLog and the severity method name. Not very useful...

I have a suggested patch to JavaLoggingLog attached to this mail, which uses a 
StackTraceElement to determine the calling method (in the same manner as the 
java logging api) and sends that to the Logger class.

Regards,
Johan Jacobsson

Re: [Asterisk-java-devel] Suggested changes to JavaLoggingLog

[Stefan R. <ste...@re...>]

Johan Jacobsson wrote:
> Hi,
>=20
> I noticed a drawback with wrapping the java logging api in the asterisk=
-java=20
> Log framework. The class and method names printed out by the java Logge=
r is=20
> always JavaLoggingLog and the severity method name. Not very useful...
>=20
> I have a suggested patch to JavaLoggingLog attached to this mail, which=
 uses a=20
> StackTraceElement to determine the calling method (in the same manner a=
s the=20
> java logging api) and sends that to the Logger class.

Thanks for your patch, i've applied it to latest SVN trunk.

=3DStefan


--=20
reuter network consulting
Neusser Str. 110
50760 Koeln
Germany
Telefon: +49 221 1305699-0
Telefax: +49 221 1305699-90
E-Mail:  ste...@re...
Jabber:  ste...@re...

Steuernummern 215/5140/1791 USt-IdNr. DE220701760