At 14:24 04.06.2001 -0400, you wrote:
>The rules for XML serialization/deserialization can be external to
>the LoggingEvent itself. Only when a remote logging event gets ready
>to go across the wire, it would inspect the LoggingEvent object and
>build the appropriate XML representation. This way, only the people
>using remote logging will need an XML parser... just the same way
>that only the people using the DOMConfiguration need an XML parser
>today.
>
>I recently did a distributed system using Apache SOAP precisely to
>combat the kind of brittleness you're talking about with Java
>serialization. In Apache SOAP, if the object you wish to serialize
>to XML follows standard JavaBean conventions... it's automatic!
>Otherwise, they have a very simple framework for writing your own
>custom serialzers and deserializers...
Did it work? Did you overcome the brittleness? What happens to code on the receiving
end that relies on the existence of field X and discovers that it is no longer there?
Regards, Ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]