Because message is an Object and not all Objects are serializable.
Hence, they serialize the rendered message instead. I know you don't
want to do it this way, but the solution is to place the renderers on
the client, not the server. Is there any reason why the renderer can't
be placed on the client? (Other than it's harder to manage and
control?)
-- Don
--- [EMAIL PROTECTED] wrote:
> Hi,
>
> Question, what was the rationale behind not serializing the
> "message"
> field in the LoggingEvent? This would have been helpful so that we
> could
> send the object remotely to a Log server and then use Renderers on
> the
> server to format the message.
>
>
> Thanks,
> - Tim
>
> ____________________________________________________
> Timothy G. Mullé
> Senior Software Architect
> Reuters Valley Forge Solutions Center
> 1000 Madison Avenue
> Norristown, PA 19403-2432
>
> Phone: (610) 650-8600 x8340
> Fax: (610) 650-8170
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
