When you use the include url="file.xml"... the contents of file.xml are parsed (correct word?) with the main.xml as if it was all one continuous file. (I'm pretty sure that's how Klaus explained it to me)
yes, that's right

the <includes> are resolved while loading the main xml, it internally becomes one big file/structure,
also note - if there are two or more times the same definition - then the order of them is important!
the xml is parsed from top to down, so the latest one is that, that will be finally set!
e.g.
|
Quellcode
|
1
2
3
|
<events onxmlcomplete="trace(1. this will be never shown, because the next definitions will overwrite it);"/>
<events onxmlcomplete="trace(2. this will be never shown too);"/>
<events onxmlcomplete="trace(3. this text will be finally shown);"/>
|
or the same with includes:
main.xml:
|
Quellcode
|
1
2
|
<events onxmlcomplete="trace(will not be shown);" />
<include url="sub.xml" />
|
sub.xml:
|
Quellcode
|
1
|
<events onxmlcomplete="trace(this will be shown);" />
|
the main.xml and sub.xml finally loaded become internally this code:
|
Quellcode
|
1
2
|
<events onxmlcomplete="trace(will not be shown);" />
<events onxmlcomplete="trace(this will be shown);" />
|
so it should also be possible to solve this problem by resorting the xml code
best regards,
Klaus