Well, I'm quite confused about exactly why log4j1.2 events don't
quite have all the info when read into a 1.3 runtime (specifically
MDC). I can only surmise that the reason is that in 1.2 the field is
called 'mdcCopy' and is a Hashtable, and in 1.3 it's called
'properties' and is a Map and
Paul Smith wrote:
On 05/04/2007, at 6:51 AM, Jess Holle wrote:
I didn't know about the MDC treatment -- I'll have to look into that.
Otherwise, I knew that #2 and #3 were covered by the existing
Chainsaw. I just didn't want to give up any of that to get #1
covered -- and don't personally see
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
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
