maxwell wrote: > We just installed v4.4.0 of XXE Pro on our Windows XP machines, upgrading > from v4.1. We are now getting an error msg when we start up XXE on > non-admin accounts; I don't believe the error msg appears when we start XXE > from an admin account. > > The error msg is as follows: > ------------------ > Errors found in plug-ins > com.xmlmind.xmleditext.fop1_foprocessor.FOP > cannot create XSL-FO processor plug-in > "com.xmlmind.xmleditext.fop1_foprocessor.FOP": > com.xmlmind.xmleditext.fop1_foprocessor.FOP.setPreferences(Lcom/xmlmind/util/Preferences;)V > com.xmlmind.xmleditext.xep_foprocessor.XEP > cannot create XSL-FO processor plug-in > "com.xmlmind.xmleditext.xep_foprocessor.XEP": > com.xmlmind.xmleditext.xep_foprocessor.XEP.setPreferences(Lcom/xmlmind/util/Preferences;)V > com.xmlmind.xmleditext.xfc_foprocessor.XFC > cannot create XSL-FO processor plug-in > "com.xmlmind.xmleditext.xfc_foprocessor.XFC": > com.xmlmind.xmleditext.xfc_foprocessor.XFC.setPreferences(Lcom/xmlmind/util/Preferences;)V > ------------------- > There was a report of a similar error msg on this mailing list a couple > years ago, but unless I'm mistaken that was from a different cause. > > We in fact are not using the FO plugin (we are using the WebDAV plugin, > which shows up as version 2.1.0 for XXE 4.4.0). That is, the FO plugin > shows up under the list of plugins that we could install, not under the > plugins that we could uninstall.
The add-on manager cannot see the add-ons pointed to using the XXE_ADDON_PATH variable, only those found the two addon/ directories of XXE. (We do not plan to remove this limitation.) > We do have directories under our group > 'addon' directory (the one pointed to by our XXE_ADDON_PATH variable) which > contain the old FO plugins (labeled 'fop1_foprocessor-4_1_0', > 'xep_foprocessor-4_1_0', and 'xfc_foprocessor-4_1_0'). That explains the error messages, which are correct, legitimate, error messages reported by Java[tm]'s ``dynamic linker''. As of XXE v4.2 (http://www.xmlmind.com/xmleditor/changes.html), the XSL-FO processor plug-ins have changed. They are now required to support user preferences. This is not the case of the old plug-ins you cannot delete. (Such old plug-ins have been designed to work with XXE v4.1 and no other version.) That makes the old plug-ins totally incompatible with XXE v4.2+. Note that the add-on manager automatically detects this when you upgrade XXE and suggests to automatically upgrade the add-ons too. But once again, all the add-ons pointed to using the XXE_ADDON_PATH variable are assumed to managed by hand. They are out of the scope of XXE's add-on manager. > For some reason I > can't delete these, as they keep showing up as being in use, although AFAIK > no one has XXE open when I do this. We do not appear to have any FO > plugin-related files in our XXE install directories (i.e. under C:\Program > Files\XMLmind_XML_Editor\addon), nor under our user-specific XXE > configuration directory (C:\Documents and Settings\maxwell\Application > Data\XMLmind\XMLEditor4\addon). > > This does not appear to be causing us any problem, apart from the annoyance > of responding to the error msg when we start XXE. I'm sorry but I really don't see how I can help you. If I understand what happens to you, you *absolutely* *need* to delete the directories labeled 'fop1_foprocessor-4_1_0', 'xep_foprocessor-4_1_0', and 'xfc_foprocessor-4_1_0', found in the addon/ directory pointed to by your XXE_ADDON_PATH variable[*]. If you cannot delete these directories, this has nothing to do with XXE. This is caused by Windows (a zombie process which keeps the files opened, preventing them from being deleted?). This happened to me with software other than XXE. I don't remember what I did to delete such unwanted files (disconnect from the network the machine on which the files are stored, then press F8 to reboot this machine in safe mode, then delete the files?) --- [*] An alternative is to get rid of the XXE_ADDON_PATH variable and instead to deploy XXE using Java Web Start.
