This is related slightly to the wishlist item I posted at XML Aware Forms. While attempting to deal with this I discovered that my XML document has duplicate Timeline element references in two places, one defines the timeline of the overall project and the other defines a timeline associated with individual work items of the project. The schemaTranslator.xsl generates two duplicate XSElement references for this datasource. It so happens that my structure is the same, so the duplicate reference is benign, though I would imagine in a general case that duplicate elements won't necessarily be the same and in this case, the second datasource declaration wins.
So the SchemaSet takes the XSD hierarchy and flattens it, losing the context (knowledge of an element's container) in the process.
This won't be a problem for me as I can enforce the rule that structures used throughout the system must be identical so duplicates in my SchemaSet aren't a problem.
I have a second issue to solve, and that's when I have Lists inside of Lists. The ListGrid doesn't handle nested tables, so I'll need to devise a different strategy for handling this case. Something for me to think about over the weekend.
So the SchemaSet takes the XSD hierarchy and flattens it, losing the context (knowledge of an element's container) in the process.
This won't be a problem for me as I can enforce the rule that structures used throughout the system must be identical so duplicates in my SchemaSet aren't a problem.
I have a second issue to solve, and that's when I have Lists inside of Lists. The ListGrid doesn't handle nested tables, so I'll need to devise a different strategy for handling this case. Something for me to think about over the weekend.
Comment