Xml-DataSource and BO-DataSource behave totally different.
Xml-DataSource and BO-DataSource behave totally different.
I have a nested "Master-Child-Subchild" Business-Object.
After registration it's a well nested tree.
The relations fit, the semantic is correct and its nice to work with.
- So far so good. -
But if i use an "Xml-File" as DataSource, which is an exact representation (in fact an XMl-Serialization) of
the BO, its's *not* nested. Objects are all on the same level, an there is a strange structure of generated
IDs and Parent-Objects. (Even an explicit xsd, which describes the nested-tree-structure doesn't change
that behaviour.)
Is there a solution for that problem? (I've read, the BO-Engine was redesigned some times ago, and previously
it behaved like the "XmlDataEngine" obviously still does. Are there plans to update the XmlDataEngine also?)
Thx for any reply...
I have a nested "Master-Child-Subchild" Business-Object.
After registration it's a well nested tree.
The relations fit, the semantic is correct and its nice to work with.
- So far so good. -
But if i use an "Xml-File" as DataSource, which is an exact representation (in fact an XMl-Serialization) of
the BO, its's *not* nested. Objects are all on the same level, an there is a strange structure of generated
IDs and Parent-Objects. (Even an explicit xsd, which describes the nested-tree-structure doesn't change
that behaviour.)
Is there a solution for that problem? (I've read, the BO-Engine was redesigned some times ago, and previously
it behaved like the "XmlDataEngine" obviously still does. Are there plans to update the XmlDataEngine also?)
Thx for any reply...
Comments
XML-datasource reads the xml file into the DataSet using the code -
dataSet.ReadXML(xmlFile);
then registers all the tables in this dataset. So the xmlfile must be DataSet-compatible.