summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBenjamin Paassen <bpaassen@techfak.uni-bielefeld.de>2015-02-15 21:56:00 +0100
committerBenjamin Paassen <bpaassen@techfak.uni-bielefeld.de>2015-02-15 21:56:00 +0100
commit40f7df390f00f85c17bd0e6527ec4ba19cbce4fc (patch)
tree4897ed0d450070f93b2450958f98e230e363cfdb
parent2544749215bc2465bfeca431e271110ca86d8a83 (diff)
swapped order of field declarations in comments domain.
-rw-r--r--testdata/xmlparser/comments_domain.oxm18
1 files changed, 9 insertions, 9 deletions
diff --git a/testdata/xmlparser/comments_domain.oxm b/testdata/xmlparser/comments_domain.oxm
index 4d8c531..6add2b3 100644
--- a/testdata/xmlparser/comments_domain.oxm
+++ b/testdata/xmlparser/comments_domain.oxm
@@ -4,12 +4,12 @@
<!-- an annotation comment -->
<annotation name="comment">
- <field name="content">
- <childRef ref="book.paragraph"/>
- </field>
<field name="replies" isSubtree="true">
<childRef ref="reply"/>
</field>
+ <field name="content">
+ <childRef ref="book.paragraph"/>
+ </field>
</annotation>
<!-- an point-like structure comment. -->
@@ -17,12 +17,12 @@
<!-- Is there a chance to prevent users from having to redefine these
two fields in comment and reply? Could we use a fieldRef here?
Or would that be circular? -->
- <field name="content">
- <childRef ref="book.paragraph"/>
- </field>
<field name="replies" isSubtree="true">
<childRef ref="reply"/>
</field>
+ <field name="content">
+ <childRef ref="book.paragraph"/>
+ </field>
<parentRef ref="book.paragraph">
<fieldRef ref="$default"/>
</parentRef>
@@ -30,11 +30,11 @@
<!-- note that replies are organized in a tree fashion: One can also reply
to a reply -->
<struct name="reply">
- <field name="content">
- <childRef ref="book.paragraph"/>
- </field>
<field name="replies" isSubtree="true">
<childRef ref="reply"/>
</field>
+ <field name="content">
+ <childRef ref="book.paragraph"/>
+ </field>
</struct>
</domain>