Page 1 of 1
XML Report - strange beaviour
Posted: Mon Feb 04, 2013 4:06 pm
by tpontow
Hello,
i have two XML reports for testing. The first has the following xml data with only one tag <Testdaten> and no further hierarchies:
Code: Select all
<Testdaten Wert1="abcd" Wert2="1" Wert3="12.67" Wert4="True" Wert5="67"></Testdaten>
With that no data is displayed in my report.
After changing the structure to
Code: Select all
<Root Ident="12">
<Testdaten Wert1="abcd" Wert2="1" Wert3="12.67" Wert4="True" Wert5="67"/>
</Root>
i can see data in my report for <Testdaten> and as well for <Root>.
Attached i have both xml data files, xsd files and report files. Can you tell me why i see no data in report / preview for the first structure with no hierarchies?
Thanks
Thorsten
Re: XML Report - strange beaviour
Posted: Tue Feb 05, 2013 6:12 am
by HighAley
Hello.
We use XMLReader class of .Net Framework to parse XML files.
Due to W3C XML Recommendations where the .Net Framework reference to, there should be a root element in the xml file.
Thank you.
Re: XML Report - strange beaviour
Posted: Tue Feb 05, 2013 7:50 am
by tpontow
Ok, i think you mean that W3C document which says:
2.1 Well-Formed XML Documents
[
Definition: A textual object is a well-formed XML document if:]
1. Taken as a whole, it matches the production labeled document.
2. It meets all the well-formedness constraints given in this specification.
3. Each of the parsed entities which is referenced directly or indirectly within the document is well-formed.
Document
[1]
document
::=
prolog element Misc*
Matching the document production implies that:
1. It contains one or more elements.
2. [Definition: There is exactly one element, called the root, or document element, no part of which appears in the content of any other element.] For all other elements, if the start-tag is in the content of another element, the end-tag is in the content of the same element. More simply stated, the elements, delimited by start- and end-tags, nest properly within each other.
[Definition: As a consequence of this, for each non-root element C in the document, there is one other element P in the document such that C is in the content of P, but is not in the content of any other element that is in the content of P. P is referred to as the parent of C, and C as a child of P.]
By this definition my first code sample above is well formed with one element which is also the root (<Testdaten>). I don't understand why i need an extra artificial root element? So i don't understand why my first xml sample can't be used as data for xml reports.
Thanks
Thorsten
Re: XML Report - strange beaviour
Posted: Tue Feb 05, 2013 8:35 am
by tpontow
I changed my data structure. If i have no subelements in my generated xml data i wrap an artifical root element around it. So, i can live with that. It's ok for me.
Thanks for the information
Thorsten Pontow
Re: XML Report - strange beaviour
Posted: Wed Feb 06, 2013 5:42 am
by HighAley
Hello.
Sorry, again. This is a behaviour of the
XMLReader class of the .Net Framework. We can't affect it.
It's good that you have found the solution of your problem.
Thank you.