You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by David Wall <dw...@Yozons.com> on 2001/04/26 04:08:42 UTC
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
Use of the mapType with beans ...
Posted by Jean-Guillaume LALANNE <je...@coming.fr>.
Hi,
Has anyone already used the mapType in the apache SOAP version ?
I have seen a MapSerializer in the soap encoding package but I haven't seen
any reference
to this type in the SOAP specification. Something like SOAP-ENC:mapType ...
I'd like to use this type with beans inside ...
Is it possible and first of all portable !?!?
I mean, does MS SOAP will accept such a type ?
Any tip is welcome.
Thanx
Jean-Guillaume LALANNE
Software Architect
COMING
www.coming.fr
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Use of the mapType with beans ...
Posted by Jean-Guillaume LALANNE <je...@coming.fr>.
Hi,
Has anyone already used the mapType in the apache SOAP version ?
I have seen a MapSerializer in the soap encoding package but I haven't seen
any reference
to this type in the SOAP specification. Something like SOAP-ENC:mapType ...
I'd like to use this type with beans inside ...
Is it possible and first of all portable !?!?
I mean, does MS SOAP will accept such a type ?
Any tip is welcome.
Thanx
Jean-Guillaume LALANNE
Software Architect
COMING
www.coming.fr
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: common practice for serializing/deserializing complex object graphs
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
"R. Mark Volkmann" wrote:
> I don't have much experience with this yet, but it is my opinion that the
> DOM strategy is the best. It seems to have the highest probability of
> working correctly when the other end is written in a language other than
> Java. If you choose to use any of the other approaches then you have to code
> the other side so it knows how to serialize/deserialize in the same way that
> the Java code did it. How would you formally describe that? If you choose
> the DOM strategy then you can describe it using a DTD or XML Schema.
>
> I'd love to hear what others think about this ... especially if you disagree
> with me!
we decided in SoapRMI that for mapping we will not serialize directly java
beans but map them (if necessary) to and from XML on-the-wire representation.
you can also add specialized handler that will (de)serialize java object from
any XML (as long as it is self contained or follows SOAP section 5 encoding
rules for use of id/href).
thanks,
alek
--
Aleksander Slominski, LH 316, IU, http://www.extreme.indiana.edu/~aslom
As I look afar I see neither cherry Nor tinted leaves Just a modest hut
on the coast In the dusk of Autumn nightfall - Fujiwara no Teika(1162-1241)
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: common practice for serializing/deserializing complex object graphs
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
"R. Mark Volkmann" wrote:
> I don't have much experience with this yet, but it is my opinion that the
> DOM strategy is the best. It seems to have the highest probability of
> working correctly when the other end is written in a language other than
> Java. If you choose to use any of the other approaches then you have to code
> the other side so it knows how to serialize/deserialize in the same way that
> the Java code did it. How would you formally describe that? If you choose
> the DOM strategy then you can describe it using a DTD or XML Schema.
>
> I'd love to hear what others think about this ... especially if you disagree
> with me!
we decided in SoapRMI that for mapping we will not serialize directly java
beans but map them (if necessary) to and from XML on-the-wire representation.
you can also add specialized handler that will (de)serialize java object from
any XML (as long as it is self contained or follows SOAP section 5 encoding
rules for use of id/href).
thanks,
alek
--
Aleksander Slominski, LH 316, IU, http://www.extreme.indiana.edu/~aslom
As I look afar I see neither cherry Nor tinted leaves Just a modest hut
on the coast In the dusk of Autumn nightfall - Fujiwara no Teika(1162-1241)
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: common practice for serializing/deserializing complex object graphs
Posted by "R. Mark Volkmann" <vo...@home.com>.
----- Original Message -----
From: "David Wall" <dw...@Yozons.com>
To: <so...@xml.apache.org>
Sent: Wednesday, April 25, 2001 9:08 PM
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.
I don't have much experience with this yet, but it is my opinion that the
DOM strategy is the best. It seems to have the highest probability of
working correctly when the other end is written in a language other than
Java. If you choose to use any of the other approaches then you have to code
the other side so it knows how to serialize/deserialize in the same way that
the Java code did it. How would you formally describe that? If you choose
the DOM strategy then you can describe it using a DTD or XML Schema.
I'd love to hear what others think about this ... especially if you disagree
with me!
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: common practice for serializing/deserializing complex object graphs
Posted by "R. Mark Volkmann" <vo...@home.com>.
----- Original Message -----
From: "David Wall" <dw...@Yozons.com>
To: <so...@xml.apache.org>
Sent: Wednesday, April 25, 2001 9:08 PM
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.
I don't have much experience with this yet, but it is my opinion that the
DOM strategy is the best. It seems to have the highest probability of
working correctly when the other end is written in a language other than
Java. If you choose to use any of the other approaches then you have to code
the other side so it knows how to serialize/deserialize in the same way that
the Java code did it. How would you formally describe that? If you choose
the DOM strategy then you can describe it using a DTD or XML Schema.
I'd love to hear what others think about this ... especially if you disagree
with me!
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org