[SoapRMI] Serialization
Romain Quilici
Romain.Quilici_at_sophia.inria.fr
Thu, 6 May 2004 18:18:57 +0200
C'est un message de format MIME en plusieurs parties.
------=_NextPart_000_06FA_01C43396.98EFCD60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I just start to use XSOAP and I have a few questions about serialization =
of complex java objects.
By complex I mean, java Objects that do not follow the get/set pattern, =
and cannot be represented by an XML tree.
=20
First do I have to implement my own serializer/deserializer ?
To be more precise, I work on a java library that facilitates =
distributed computation. Our objects communicate through RMI.=20
I would like them to be able to communicate with SOAP.
Our objects have a part called body which is a RemoteObject(SUN). At =
this point RMI manages all the serialization. My idea was to add another =
body that is a XSOAP Remote Object. But since request or reply between =
remote objects can contain very complex type (like remote objects =
themselves, objects with an activity(thread)....), I wonder how the =
default serialization behaves, and if I have to implement my own =
mechanism.
Also how the default mechanism handles serialization of XSOAP Remote =
Object(is it like RMI, where Remote Object are converted to stub)?
I saw in the mailing list that nothing is done for dynamic classloading, =
is it still true ?=20
Thanks for your answer
Romain
------=_NextPart_000_06FA_01C43396.98EFCD60
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4937.800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I just start to use XSOAP and I have a =
few=20
questions about serialization of complex java objects.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>By complex I mean, java Objects =
that do not=20
follow the get/set pattern, and cannot be represented by an XML=20
tree.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>First do I have to implement my own=20
serializer/deserializer ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>To be more precise, I work on a java =
library that=20
facilitates distributed computation. Our objects communicate =
through RMI.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I would like them to be able to =
communicate with=20
SOAP.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Our objects have a part called body =
which is a=20
RemoteObject(SUN). At this point RMI manages all the serialization. My =
idea was=20
to add another body that is a XSOAP Remote Object. But since =
request or=20
reply between remote objects can contain very complex type (like remote =
objects=20
themselves, objects with an activity(thread)....), I wonder how the =
default=20
serialization behaves, and if I have to implement my own =
mechanism.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Also how the default mechanism handles=20
serialization of XSOAP Remote Object(is it like RMI, where Remote Object =
are=20
converted to stub)?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I saw in the mailing list that nothing =
is done for=20
dynamic classloading, is it still true ? </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for your answer</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Romain</FONT></DIV></BODY></HTML>
------=_NextPart_000_06FA_01C43396.98EFCD60--