DO NOT REPLY [Bug 4284] - Java serialization problematic for broad trees

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4284>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4284

Java serialization problematic for broad trees





------- Additional Comments From rahul.srivastava@sun.com  2001-11-02 23:57 -------
Do you mean to say that small DOM trees when returned from EJBs gets serialized
/ deserialized correctly from app server to the web server, but, is problematic
in case of large trees. That is, they consume lot of memory. Well, huge DOM
trees (e.g. thousands of children under one node) definitely consume memory.
But, this serialization between the app server and web server over the network
is the responsibility of the JVM. It has nothing to do with the serialization
implementation of xerces. It will be nice if you can be more clear about the BUG
in xerces in this case, so that one can look into this.

Alternatively, you can use xerces serialization implementation to serialize the
DOM created and then return this serialized xml file from the EJB, which can be
deserialized at the other end.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org