FYI: At the Logging API session at JavaOne, the presenter mentioned exactly
that issue -- the "unreliability" of the stack-trace information. He said
they (the JSR47 team at Sun) talked to the VM people to see if they could
get it fixed and were told that it's not possible. The information will
At 08:08 03.07.2001 -0700, you wrote:
>Hi Pavel,
>
>I agree that localization resource bundles are important. In fact, the
>only thing I liked better about jlog (called jras back then) was that it
>was designed primarily to use localization bundles. Methods where the
>string was hard-coded were
Hi Pavel,
I agree that localization resource bundles are important. In fact, the
only thing I liked better about jlog (called jras back then) was that it
was designed primarily to use localization bundles. Methods where the
string was hard-coded were provided merely as a convenience feature for
Hi,
In log4j there is capability of using localized messages. I use this
capability for defining log messages text due to message ID. Localization
can be configured only at run-time. But why there is no capability of
defining log messages bundles with configuration files?
I think, that configur
At 13:31 03.07.2001 +0400, you wrote:
>Hi,
>
>How about adding capability of localization configuration via configuration
>files?
"Localization configuration" is not a configuration option. It is irreversible as far
as things are irreversible in software. It also completely changes the way the l
Hi,
How about adding capability of localization configuration via configuration
files?
Paul Mykhataew,
ICQ #33733798
begin 600 winmail.dat
M>)\^(A$)`0:0"``$```!``$``0>0!@`(XP0```#G``$(@`<`
M&$E032Y-:6-R;W-O9G0@36%I;"Y.;W1E`#$(`06``P`.T0<'``,`
M#0`?``\``@`?`0$@@`,`#@```-$'!P
ceki01/07/03 02:24:44
Modified:docs critique.html download.html earlier.html index.html
src/xdocs download.xml earlier.xml index.xml
Log:
- Changes to HTML files. Added Chainsaw to the list of 3rd-party software.
Revision ChangesPath
1.16 +27
At 12:34 03.07.2001 +0400, Pavel Muhataev wrote:
>Hello Ceki Gulcu
>
>> Some competing logging packages offer the functionality of
>> dumping objects. I am not sure automated object dumps are a
>> good idea. For the following reasons:
>>
>> 1) The amount of (automated) output per object can be
Hello Ceki Gulcu
>>> Some competing logging packages offer the functionality of
>>> dumping objects. I am not sure automated object dumps are a
>>> good idea. For the following reasons:
>>>
>>> 1) The amount of (automated) output per object can be large
>>> which may cause scrolling-blindness
Hello Ceki Gulcu
> Some competing logging packages offer the functionality of
> dumping objects. I am not sure automated object dumps are a
> good idea. For the following reasons:
>
> 1) The amount of (automated) output per object can be large
> which may cause scrolling-blindness.
>
> 2) T
Hi
> 1) It's already provided via the "locationInfo" in
> LoggingEvent. If you want to see it, use your layout's means
> for doing so. (For example, PatternLayout will show
> everything you mentioned and more.) It's usually not used
> because it dramiticly slows things down, but if you've
Hello Pavel,
At 12:07 03.07.2001 +0400, Pavel Muhataev wrote:
>Hi
>
>> 1) It's already provided via the "locationInfo" in
>> LoggingEvent. If you want to see it, use your layout's means
>> for doing so. (For example, PatternLayout will show
>> everything you mentioned and more.) It's usual
12 matches
Mail list logo
