> From: Scott Hernandez [mailto:ScottHernandez@;hotmail.com]
>
> The unfortunate side affect of doing this entity inclusion is that the
> partX.xml files are xml fragments and not well-formed documents. XLink
> provides a better alternative but is implementation bound. Not all xml
> processors/parsers support the XLink syntax.
Well, aside from missing the <?xml version="1.0"?> directive, the entity
inclusion fragments can be well-formed documents.
Part1.xml could be this:
<commands>
<command name="blah">
...
</command>
</commands>
Part2.xml this:
<commands>
<command name="blah2">
...
</command>
</commands>
Using XSL certainly would work, but it seems like overkill for this
purpose.
Jeff
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
[INVALID FOOTER]
