> Message rendering is done prior to serialization. After serialization
> calling getMessage and getRenderedMessage always give the same result
> regardless of how you configure the server (receiving) side. Object
> rendering should be configured on the clients. HTH,
Hi Ceki,
I'd always assumed the message rendering would be provided by the appender
sending the LoggingEvent.
If I'd had an appender with a pattern layout such as [%-5p] [%d{DATE}]
[%C.%M] - %m%n, and made a
call such as log.debug("Hello World"), I'd expect two different strings in
the serialized LoggingEvent.
getMessage() would return Hello World, and
getRenderedMessage() would return [DEBUG] [20 Dec 2002 10:07:00,513]
[myClass.myMethod] - Hello World
If the rendering is provided on the client, then how can I render the
message?
Do I simply build it up using the components (using LocationInformation,
Message, Timestamp etc) or is there a utility class to help with this
rendering?
Regards,
Peter
********************************************************************
This email may contain information which is privileged or confidential. If you are not
the intended recipient of this email, please notify the sender immediately and delete
it without reading, copying, storing, forwarding or disclosing its contents to any
other person
Thank you
Check us out at http://www.syntegra.com
********************************************************************
