RE: common practice for serializing/deserializing complex object graphs

["Prabhakar, V" <V....@compaq.com>]

I am curious as to how does one write custom serializer/deserialzer? Any
guideliens/pointers would help.

Thanks,

-V Prabhakar

-----Original Message-----
From: David Wall [mailto:dwall@Yozons.com]
Sent: Wednesday, April 25, 2001 10:09 PM
To: soap-user@xml.apache.org
Subject: common practice for serializing/deserializing complex object
graphs


I'm trying to figure out what are considered the best or most common
practice for handling the sending and receiving of complex object
graphs.
Would most people create them so that all of the eventually fit the
javabeans get/set properties so that only byte, String, int/long/short,
etc.
are returned (or Array of those types) and use the BeanSerializer?

Or would most people write a custom serializer/deserializer?

Or would most people store the data into a DOM and use "literal xml"
encoding?

Or would they use XMI (and is XMI different from BeanSerializer)?  Does
XMI
still need the separate XML4J or has that code been integrated into
Apache
SOAP?

It would seem that a javabean strategy would be the easiest from a java
server programming perspective, but that a DOM strategy may be the most
portable -- and a custom serializer would be the most platform-centric
and
likely not portable, even if eventually going to Axis or other soap
implementations.

What's the world doing out there to get the job done?

Thanks,
David


---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org