summaryrefslogtreecommitdiff
path: root/testdata/xmlparser/comments_domain.oxm
diff options
context:
space:
mode:
Diffstat (limited to 'testdata/xmlparser/comments_domain.oxm')
-rw-r--r--testdata/xmlparser/comments_domain.oxm24
1 files changed, 12 insertions, 12 deletions
diff --git a/testdata/xmlparser/comments_domain.oxm b/testdata/xmlparser/comments_domain.oxm
index 1336b47..4d8c531 100644
--- a/testdata/xmlparser/comments_domain.oxm
+++ b/testdata/xmlparser/comments_domain.oxm
@@ -4,11 +4,11 @@
<!-- an annotation comment -->
<annotation name="comment">
- <field name="content" isSubtree="true">
- <child ref="book.paragraph"/>
+ <field name="content">
+ <childRef ref="book.paragraph"/>
</field>
<field name="replies" isSubtree="true">
- <child ref="reply"/>
+ <childRef ref="reply"/>
</field>
</annotation>
@@ -17,24 +17,24 @@
<!-- 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" isSubtree="true">
- <child ref="book.paragraph"/>
+ <field name="content">
+ <childRef ref="book.paragraph"/>
</field>
<field name="replies" isSubtree="true">
- <child ref="reply"/>
+ <childRef ref="reply"/>
</field>
- <parent name="book.paragraph">
- <fieldRef name="$default"/>
- </parent>
+ <parentRef ref="book.paragraph">
+ <fieldRef ref="$default"/>
+ </parentRef>
</struct>
<!-- note that replies are organized in a tree fashion: One can also reply
to a reply -->
<struct name="reply">
- <field name="content" isSubtree="true">
- <child ref="book.paragraph"/>
+ <field name="content">
+ <childRef ref="book.paragraph"/>
</field>
<field name="replies" isSubtree="true">
- <child ref="reply"/>
+ <childRef ref="reply"/>
</field>
</struct>
</domain>