[
Lists Home |
Date Index |
Thread Index
]
- From: Sasha Nakhimovsky <sasha@mail.colgate.edu>
- To: "'haustein@ls8.cs.uni-dortmund.de'" <haustein@ls8.cs.uni-dortmund.de>,Andrew Layman <andrewl@microsoft.com>
- Date: Mon, 24 Jul 2000 10:26:55 -0400
Can SOAP serialize an arbitrary Java object without loss of data? What are
the constraints, if any? A study of Section Five would of course yield the
answer, but I'm hoping that it already exists in a pre-packaged form.
adn
-----Original Message-----
From: Stefan Haustein [mailto:haustein@ls8.cs.uni-dortmund.de]
Sent: Monday, July 24, 2000 9:45 AM
To: Andrew Layman
Cc: xml-dev@lists.xml.org
Subject: Re: Default Namespaces - why don't they apply to attributes?
Andrew Layman wrote:
>
> SOAP section five specifically provides serialization rules for entire
> objects or graphs of objects. Its use is not limited to method calls but
is
> a general facility for serialization.
Wouldn't it be clearer to put section five into an own document, or
to give it at least a name like SSF (SOAP Serialization Format) that
can be simpler referenced than "SOAP section five"? (Oops, what does
SSF actually mean - SOAP Serialization Format or SOAP Section five? :-)
My problem is: When I mention SOAP, I first need to explain
that I do not mean HTTP+XML based RPC but the serialization format
mentioned in section five of the spec...
Best,
Stefan
--
Stefan Haustein
Univ. Dortmund, FB 4, LS 8 tel: +49 231 755 2499
Baroper Str. 301 fax: +49 231 755 5105
D-44221 Dortmund (Germany) www-ai.cs.uni-dortmund.de
|