Ulrich_Laegeler at arburg.com wrote: > > just to understand it right. > > When the clipboard is pasted the nodes with ns2:inclusion attributed are > converted > to a xi:include node.
No, not at all. Internally, XXE does not operate on xi:include elements. To make it simple, xi:include elements, just like namespace prefixes, are constructs which exist only at document open and save times. Internally, XXE operate on XML nodes annotated with *properties*. Among the properties commonly used by XXE, you'll find the following properties: ns2:readOnly ns2:sourceURL ns2:inclusion The ns2:readOnly is used to mark a node as being read-only. The ns2:sourceURL is (vaguely) similar to xml:base. The ns2:inclusion property means: the node comes from an external source and has been obtained using the inclusion scheme specified in the value of this property. Example: ns2:inclusion="com.xmlmind.xml.xinclude.XInclude: href='file:/home/hussein/src/4xxe/demo/docbook-modular-book/glossary.xml' xpointer='XXE'" * We currently support *two* inclusion schemes: XInclude and DITA conref. * It is perfectly possible to develop a custom inclusion scheme which would get its XML nodes by querying a database or a web service. * Currently there are discussions about abandoning XInclude in favor of a specific inclusion scheme (? la conref) in DocBook 6. All these are very good reasons for XXE not to internally work with xi:include elements! > > And if i Rebuild the whole document (Ctrl+L) all Includes are reincluded and > rebuild. > > If the above is correct why does the ClipboardFormat.parse() command not > automatically > reinclude a deteced Inclusion node. > An xi:include element is *not* detected by ClipboardFormat.parse() as being an inclusion. Except at document open time (provided that the inclusionScheme configuration element -- http://www.xmlmind.com/xmleditor/_distrib/doc/configure/inclusionScheme.html -- has been properly used), an xi:include element conveys no special meaning. Teaching ClipboardFormat.parse() to recognize xi:include elements as inclusions is of course technically possible. However this has a very limited utility. We do not think that a lot of users copy and paste pieces of XML containing xi:include elements. On the other hand, there is no problem copying and pasting XML snippets containing inclusions between two instances of XXE. And of course, programmatically inserting inclusions in a document poses no problems. See command include -- http://www.xmlmind.com/xmleditor/_distrib/doc/commands/include.html
