[Mono-devel-list] Re: asorted xml implementation questions

ginga at kit.hi-ho.ne.jp ginga at kit.hi-ho.ne.jp
Fri Mar 28 12:10:17 EST 2003


> XmlSerializer/XmlSerializationWriter: Judging by the argument lists 
> of XmlSerializer痴 Serialize methods, it looks like the protected
> method that takes the XmlSerializationWriter is probably the real
> serializer that the other methods should call by wrapping their
> stream/textwriters/xmltextwriters/etc in an XmlSerializationWriter
> (actually a derived class of it).

I think it is right, but how do you think to go along with it?
I attached an experimental test. Serialize (object, XSW) wan't
called from Serialize (TextWriter, object).

> property must be available outside of the System.Xml assembly. 
> An example of this occurs when generating a WSDL from a
> ServiceDescription object through serialization. Element order is
> important in WSDLs, and 

Then I wonder why MS System.Web.Serivices.dll developers could
serialize ServiceDescription without such Order attribute...

Hmm... I wonder I had better dive into serialization stuff... ;)

  Atsushi Eno
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xsw.cs
Type: application/octet-stream
Size: 638 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20030329/02927ef2/attachment.obj 

More information about the Mono-devel-list mailing list