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.
>________________________________ > From: Hussein Shafie <[email protected]> >To: Jeff Hooker <[email protected]> >Cc: "'[email protected]'" <[email protected]> >Sent: Tuesday, March 13, 2012 11:58:06 AM >Subject: Re: [XXE] Document Cache in XXE 5.1.0 behaving inappropriately > >On 03/13/2012 07:08 PM, Jeff Hooker wrote: >> >> We have discovered a serious issue with caching in XXE 5.1.0. We have >> confirmed it on Windows 7. >> >> Under circumstances that are still unclear, XXE will stop looking for >> updated documents on either the local file system or (as is the more >> common case in at PMC) in the local cache managed by the CMS. Using the >> "Clear Document Cache" feature in the Preferences area addresses the >> issue. If the Document Cache feature is turned off, then turning it on, >> and clearing the cache addresses the issue. >> >> I have tested beyond any doubt that the files on the drive are not the >> files being opened (and then saved) by XXE. > > >XXE document cache has no direct influence on the file being opened by XXE. >This looks like the URLConnection cache bug already reported by another >customer. > >We have added a workaround for what seems to be a Java bug. The workaround is >found in XXE v5.2, which should be released in a couple of days. > >Description of the workaround: >--- >Workaround the following Java bug, which affected XXE when deployed as an >applet or using Java Web Start: modifying a document stored on a WebDAV >server, closing it and then immediately (that is, without exiting XXE) >reopening it, loaded the document in its original state and not in its latest, >modified, state. >--- > > > >> >> Exactly why it starts happening is unclear, but once it has started, it >> will consistently happen going forward on the affected machine. > >Please remember that we absolutely need to be able to reproduce a problem here >at XMLmind in order to fix it or to add a workaround for it. > > > >> >> At this point, more than a fix, I need a way of forcibly emptying the >> XXE document cache on every launch and before every file > open command. >> > >XXE document cache is not persistent (not stored on disk; only in memory). You >can only disable this cache and this is done once for all. > >In order to make sure that this cache is always disabled, please start XXE >with this command-line option (also supported in Java Web Start's xxe.jnlp): > >-putpref documentCache 0 > >However, I am not sure that by disabling XXE document cache the problem will >completely go away. > >See http://www.xmlmind.com/xmleditor/_distrib/doc/help/preferenceKeys.html > >See http://www.xmlmind.com/xmleditor/_distrib/doc/help/command_line_usage.html > > >
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
