Thanks Mark et al, I shall look at all the suggestions.
Regarding immutability what was more of an issue for us was that although the LoggingEvent is currently immutable, we want to protect ourselves in case any future versions of LoggingEvent are not.
I am a little troubled by your line of reasoning.
Regards and thanks, Damian ONeill.
Quoting Mark Womack <[EMAIL PROTECTED]>:
> In version 1.3 a constructor was added to LoggingEvent so that it could be
> created with given information. This is used by some of the
> appender/receiver combos by Scott Deboy that do not serialize LoggingEvent
> obejcts across sockets. Instead they serialize XML, etc.
>
> That might get you what you want. But regardless, once the LoggingEvent has
> been constructed in the given log4j environment, it is considered immutable
> that point and cannot be subsequently modified.
>
> -Mark
--
Ceki For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
