S
Sean
Hi, I'm trying to manage the serialization of circular references (which are
valid) and multiple references to the same object.
Normal XML serialization can't handle these at all, circular references
cause it to fail and multiple references to the same object just give you
multiple copies of the same object (each of which could be edited
independently at the same time in InfoPath, yikes!).
One way around this is to use a SOAP formatter to serialize the object
hierarchy, as it can handle circular references and with multiple object
references it preserves the references rather than just copying the object.
Unfortunately when I load the SOAP-formatted XML into InfoPath it look
hideous, the object hierarchy for the DataSet is pretty unusable.
Is there any way to get InfoPath to represent this in a more user-friendly
way? Or alternatively is it possible to use the same schema for the
datasource as I currently do (i.e. the one I generate fro mthe assembly
using XSD.exe) and yet send it SOAP-formatted XML.
By the way by SOAP-formatted I don't just mean that it has SOAP headers
around the XML, I mean that I've used the SOAP formatter in
System.Runtime.Serialization.
Does anyone have any ideas on this?
Thanks in advance.
Sean
valid) and multiple references to the same object.
Normal XML serialization can't handle these at all, circular references
cause it to fail and multiple references to the same object just give you
multiple copies of the same object (each of which could be edited
independently at the same time in InfoPath, yikes!).
One way around this is to use a SOAP formatter to serialize the object
hierarchy, as it can handle circular references and with multiple object
references it preserves the references rather than just copying the object.
Unfortunately when I load the SOAP-formatted XML into InfoPath it look
hideous, the object hierarchy for the DataSet is pretty unusable.
Is there any way to get InfoPath to represent this in a more user-friendly
way? Or alternatively is it possible to use the same schema for the
datasource as I currently do (i.e. the one I generate fro mthe assembly
using XSD.exe) and yet send it SOAP-formatted XML.
By the way by SOAP-formatted I don't just mean that it has SOAP headers
around the XML, I mean that I've used the SOAP formatter in
System.Runtime.Serialization.
Does anyone have any ideas on this?
Thanks in advance.
Sean