Unfortunately, the issue is not fixed after all. It still persists, even in the native XXE docbook5 plugin, when the following conditions are met:
1. User 1 opens a docbook XML document containing one or more xincludes. The xinclude content is displayed in the document. 2. User 2 opens the content of one of the xincludes on another computer, edits it, and checks it in. 3. User 1 uses CTRL-SHIFT-E to open the xinclude for editing. At that point, regardless of the document cache setting, XXE will open the outdated document. It must be emphasized that the *correct* version of the document is loaded into the computer's local cache, but it is not opened by XXE. 4. When the user edits, saves, and closes the document, the outdated version of the content is saved to the repository. Clearing the XXE cache does not clear the outdated content; restarting XXE does. Jeff. >________________________________ > From: Hussein Shafie <[email protected]> >To: Jeff Hooker <[email protected]> >Cc: "'[email protected]'" <[email protected]> >Sent: Wednesday, March 14, 2012 11:17:57 AM >Subject: Re: [XXE] Document Cache in XXE 5.1.0 behaving inappropriately > >On 03/14/2012 06:03 PM, Jeff Hooker wrote: >> The culprit was our custom Docbook add-on. >> >> We defined the inclusionScheme and related linkType content in the main >> configuration file for the add-on, but it was also defined in the >> docbook 5 package that our custom add-on included. Removing the >> declarations from our custom add-on removed the problem. > >Thank you for this information. > >However I still don't understand what happened and why redefining >inclusionScheme and/or linkType in your customization could cause XXE to run >amok. > > >
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
