Re: Web Service Session State

So you basically created your own XML generator based on the values
passed.
I can't see the advantage of writing your own XML if the data
definitions are available...

Surprisingly the DTDs converted to XSDs nicely. I was able to create
Serializable classes with XSD. I was able to serialize the class <> XML
with XmlSerializer. This is a step forward. I sent you an email.

Well actually, I might be forced to use the XMLWriter anyway.
I have an element Login and I am able to use it in my code :

Login l = new Login();
l.userId = "chris";
l.password = "pass";

When I serialize I get this:
<?xml version="1.0" encoding="utf-16"?>
<Login userId="chris" password="password" />

But what is expected is this:
<?xml version="1.0" encoding="utf-16"?>
<!DOCTYPE SystemLink SYSTEM 'SystemLinkRequest.dtd'>
<System-Link>
<Login userId="chris" password="password" />
</System-Link>

And I can't just do this:
Login l = new Login();
l.userId = "chris";
l.password = "pass";
SystemLink sl = new SystemLink();
Sl.Login = l;

Since serializing the entire SystemLink class will serialize all the
fields within SystemLink class. So I need to find a way to inject the
additional metadata.


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Walden H.
Leverich
Sent: Tuesday, January 12, 2010 3:33 PM
To: .net use with the System i
Subject: Re: [SystemiDotNet] Web Service Session State

Not sure how complex the types are in the DTD, but one option is to put
the right attributes on the members and use the native XML
serialization. The other option is to just craft the XML yourself using
the XmlWriter methods. We have some code that exports from our system
for import back into OUR system, and we still found it simpler to use
the XmlWriter methods than the serializer -- you get total control over
the XML.