On Jan 10, 2005, at 4:34 PM, Ceki Gülcü wrote:
At 11:01 PM 1/10/2005, Curt Arnold wrote:
In the original message, I outlined two approaches and their
perceived drawbacks. One was just replacing sequenceCount with the
value of super.hashCode. This would likely work okay, but the
short-lifetime
At 11:01 PM 1/10/2005, Curt Arnold wrote:
In the original message, I outlined two approaches and their perceived
drawbacks. One was just replacing sequenceCount with the value of
super.hashCode. This would likely work okay, but the short-lifetime of
LoggingEvent's might result in recurring val
On Jan 10, 2005, at 3:05 PM, Ceki Gülcü wrote:
Two logging events that are identical in all other respects would
have a high likelihood of having distinct values for eventID and
acquiring the hash code would not incur an synchronization lock.
So, "all" you are suggesting is to replace
class Log
ceki2005/01/10 14:00:43
Modified:.build.xml
Log:
It's o.a.l.filter not filters.
Revision ChangesPath
1.137 +1 -1 logging-log4j/build.xml
Index: build.xml
===
RCS file: /home/cvs/
ceki2005/01/10 14:00:07
Modified:.build.xml
Log:
It's o.a.l.filter not filters.
Revision ChangesPath
1.136 +1 -1 logging-log4j/build.xml
Index: build.xml
===
RCS file: /home/cvs/
At 08:54 PM 1/10/2005, Curt Arnold wrote:
What I was suggesting as a potential approach (with the drawbacks
mentioned), is the value of hashCode at the time of creation could be
obtained and stored as a distinct member that would be be used to
distinguish objects that are identical in value in a
On Jan 10, 2005, at 12:33 PM, Ceki Gülcü wrote:
At 05:43 PM 1/10/2005, Curt Arnold wrote:
I said Object.hashCode, the underlying implementation if you had
called super.hashCode() within logging event. It has similar
characteristics to a memory address,
Yes, the Object.hashCode implementation is
At 05:43 PM 1/10/2005, Curt Arnold wrote:
I said Object.hashCode, the underlying implementation if you had called
super.hashCode() within logging event. It has similar characteristics to
a memory address,
Yes, the Object.hashCode implementation is computed over the object's
addres. However, two
On Jan 10, 2005, at 6:36 AM, Ceki Gülcü wrote:
At 06:23 AM 1/10/2005, Curt Arnold wrote:
I haven't worked any more on this, but I do intend to do so. I
thought that I would at least give a heads up that this issue isn't
dead.
The current approach has a couple of drawbacks:
it incurs a synchron
At 08:42 PM 1/9/2005, Curt Arnold wrote:
This pass at the schema was just driven by the content of input/src/xml
with no reference to the code. tests/input/xml/fallback1.xml contains an
errorHandler element and it appears to be used by
o.a.l.varia.ErrorHandlerTestCase. Is that test dead or jus
No, it does not. I would prefer if log4j did not either. Furthermore, I
also suspect that some of the other committers have changed their minds
since the last vote on the subject.
At 12:50 PM 1/10/2005, Endre Stølsvik wrote:
On Sat, 8 Jan 2005, Ceki Gülcü wrote:
| Yes, thanks. Have you tried UGL
At 06:23 AM 1/10/2005, Curt Arnold wrote:
I haven't worked any more on this, but I do intend to do so. I thought
that I would at least give a heads up that this issue isn't dead.
The current approach has a couple of drawbacks:
it incurs a synchronization for every dispatched message,
yes
it add
On Sat, 8 Jan 2005, Ceki Gülcü wrote:
| Yes, thanks. Have you tried UGLI?
Not yet.
Does it have the trace level?! :)
Endre
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
At 11:38 AM 1/9/2005, Vincent Massol wrote:
There is another solution: to use a custom logging monitor as explained here
(http://paulhammant.com/blog//000241.html) - I've done that for Cargo and it
looks good. I'm sure it is less powerful than using CL or UGLI but it has
the advantage of reducing t
Brian O'Rourke wrote:
I am quite interested in this topic. I've browsed through the Chainsaw
source code and at first blush it seems very strongly coupled with
AWT. Have you given any thought to what core pieces of Chainsaw (if
any) might be pulled further away from the UI?
Regards,
Brian O'Rourke
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4j-tests has an issue affecting its community integration.
This issue
16 matches
Mail list logo
