Hello,
for details about xapp:child / seq / occ / chc you will find a chapter 'Schema based Operations' within your X-Application documentation.
For your problem: If you use an 'iterate' attribute within your xapp:loop tag, X-Application looks into the schema and looks for a schema path to the element(s) you want to iterate. The algorithm will no valid schema path if more than one occurrence occurs between the starting point (Organization) and the end point (Classification). There are two occurrences because of the optional sequence with is internally handled as an occurrence.
To define a schema path: You can use xapp:child() where index defines the position of the element / sequence / choice within an element declaration of your schema.
The structure path from Organization to Classification is
xapp:child(1)/xapp:child(1)/xapp:child(1)/xapp:child(4)
- addresses the first sequence
- addresses the first child of the first sequence (occurrence for the optional sequence)
- addresses the nested sequence
- addresses the occurrence of the classification node.
Alterenatively you could use 'seq' / 'occ' / 'chc' instead of 'child':
xapp:seq(1)/xapp:occ(1)/xapp:seq(1)/xapp:occ(2)
Both of the paths address the occurrence node on top of the Classification node.
I hope, that small explanation helps you to understand the problem.
We are aware that the schema based paths are too complicate. Therefore, for the next version of X-Application we will offer a better support of XPath. This should simplify the access to child elements.
Bye,
Christian.
[This message was edited by Christian Freytag on 14 Jan 2003 at 08:22.]
#API-Management#webMethods#Tamino