I'm not sure that we can help you because your setup is quite unusal. --> Just guessing:
* Hard Fact: XXE add-on manager (i.e. Options|Install Add-ons) only copes with the add-ons found in XXE_install_dir/addon/ and XXE_user_preferences_dir/addon/. It completely ignores what's pointed by environment variable XXE_ADDON_PATH. * May be you had fop1_foprocessor, xep_foprocessor, xfc_foprocessor installed normally and that you sucessfully managed to uninstall them using "Options|Install Add-ons". * However those fop1_foprocessor, xep_foprocessor, xfc_foprocessor were up-to-date (compatible with XXE v4.4) and ``shadowed'' obsolete fop1_foprocessor, xep_foprocessor, xfc_foprocessor (compatible with XXE v4.1). The obsolete fop1_foprocessor, xep_foprocessor, xfc_foprocessor are those referenced by XXE_ADDON_PATH. * Now that you have uninstalled fop1_foprocessor, xep_foprocessor, xfc_foprocessor which were compatible with v4.4, XXE sees the obsolete fop1_foprocessor, xep_foprocessor, xfc_foprocessor. * The FOP plug-in has drastically changed since v4.2. See http://www.xmlmind.com/xmleditor/changes.html --- The FOP plug-in now has its preferences form in the Options|Preferences dialog box. This preferences form allows to specify which TTF fonts (e.g. arialbi.ttf) are to be embedded in the generated PDF and for each embedded font, one or more aliases (e.g. sans-serif bold italic). --- Therefore a fop1_foprocessor compatible with v4.1 cannot be compatible with v4.4. Hence the legitimate error message: 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 --> The cure: [1] You have to choose between using manually managed add-ons (variable XXE_ADDON_PATH) and automatically managed add-ons (Options|Install Add-ons). You cannot use both. [2] Please manually delete fop1_foprocessor-4_1_0 xep_foprocessor-4_1_0 xfc_foprocessor-4_1_0 from the shared folder as such add-ons are completely obsolete. These are almost certainly the cause of your problem. [3] If you choose to keep using variable XXE_ADDON_PATH, you *must* update the add-ons found there, because we cannot guarantee that an add-on compatible with XXE vX will also be compatible with XXE vY. [4] Please consider giving up the use of variable XXE_ADDON_PATH and deploying XXE using Java Web Start. Most of our customers deploying XXE for a group of users do this. maxwell wrote: > Getting back to this after a week of meetings :-( > > On Sat, 03 Apr 2010 09:51:35 +0200, Hussein Shafie <[email protected]> > wrote: >> Note that there is just a single (not ``three or so'') FOP add-on. This >> add-on is called "Apache FOP 1.x XSL-FO processor plug-in". >> >> Having ``three or so'' FOP add-ons is abnormal and is almost certainly >> the cause of your problems. > > I misspoke when I said there were three FOP add-ons; I removed three > add-ons that I interpreted as having s.t. to do with FOP. They were (I > believe) the fop1_foprocessor, the xep_foprocessor, and the > xfc_foprocessor. > >> --> Unless you have changed the location where add-ons are installed, >> the FOP add-on should installed in >> XXE_install_dir/addon/fop1_foprocessor/ (or > fop1_foprocessor-SOMETHING/). > > I have defined the variable XXE_ADDON_PATH to another path (a shared > directory), so I'm looking in that directory. That addon directory has > subdirectories > fop1_foprocessor-4_1_0 > xep_foprocessor-4_1_0 > xfc_foprocessor-4_1_0 > which matches your "fop1_foprocessor-SOMETHING/". However, I'm guessing > the 4_1_0 means XXE version 4.1.0, whereas I'm running 4.4.0 (and other > people here with a similar configuration have 4.5.0, but we all run off the > same addon directory). So that may be part of the problem. > > BTW, the other places where I might expect the FOP plugin to be (in the > XXE program directory, and in my user preferences directory) don't have any > plugins. > >> Please confirm that this directory contains a file called >> __REMOVED_XXE_ADDON__ > > There was no such file in the fop1_foprocessor-4_1_0 directory, which > instead contains a subdirectory called fop1_foprocessor, which in turn > contains a bunch of .jar, .license etc. files. > >> If you don't find XXE_install_dir/addon/fop1_foprocessor/, please try >> with XXE_user_preferences_dir/addon/fop1_foprocessor/. > > I believe that under WinXP, the latter dir should be C:\Documents and > Settings\<username>\Application Data\XMLmind\XMLEditor4\addon. That > directory is empty. > >> --> For an unknown reason, XXE didn't succeed in deleting directory >> XXE_install_dir/addon/fop1_foprocessor/ when you restarted the app after >> uninstalling the FOP add-on. > > I believe that's correct, and I'm guessing it's true because that is a > shared directory. I have write permission to that directory, but perhaps > someone else had their copy of XXE running, thereby preventing the plugin's > removal? > >> Please tell us: >> * which version of Windows (XP, Vista, 7) you are using, > XP > >> * where you have installed XXE, > C:\Program Files\XMLmind_XML_Editor > >> * where the FOP add-on has been installed (XXE_install_dir/addon/ OR >> XXE_user_preferences_dir/addon/), > S:\TTO1308\XMLEditor4\addon (the S: drive is a shared network drive) > >> * which add-ons other than FOP you have installed (MathML? JEuclid?). > We have the WebDAV plugin installed, and I use it successfully, but for > some reason it doesn't show up on the list of installed plugins (on the > "Uninstall" tab in the "Install Add-ons" dlg). > >> so we can try to reproduce the problem. -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
