[EMAIL PROTECTED] wrote: > I noticed that DocumentImpl implements Serializable (as does NodeImpl), but > several other classes (like DocumentTypeImpl) don't. I'm trying to send a > DocumentImpl back form an EJB server, and obviously it's not working. I'm > assuming that the preferred method of doing this is just to use the > serializers. I was hoping to avoid reconstructing the DOM tree. Any > thoughts?
I don't understand this one because I am able to serialize a document (the standard Serializable way) and read it back in again w/o errors. Take a look at the sample program I've attached to this message. What is your EJB server doing differently about serializing these objects? Anyway, I think it's more efficient to write the document to XML form, serialize *that*, and reparse it on the other end than to use Java serialization of Objects. The standard Serializable format on the wire is huge. -- Andy Clark * IBM, JTC - Silicon Valley * [EMAIL PROTECTED]
Serializable.java
Description: application/unknown-content-type-java_auto_file
