On Fri, 09 Apr 2010 10:37:53 +0200, Hussein Shafie <[email protected]> wrote (I've re-arranged the order):
> [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. Yes, they were; it's now working without the warning msgs. > I'm not sure that we can help you because your setup is quite unusal. > > * 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. OK, but now I'm really confused. Why name it "XXE_ADDON_PATH" if the XXE add-on manger ignores it? We used XXE_ADDON_PATH to specify a central location for our local mods to the DocBook schema, css etc. I don't want everyone to have to update their installation every time I make a change to the css. Should we be pointing to our local .rng, .css, .xxe etc. mods in some other way? XXE_USER_PREFERENCES doesn't work for this, does it? Putting it differently, *all* our local mods are configuration customizations; we have no mods that contain e.g. .jar files. Is there a better way to distribute this kind of modification automatically, without the end users having to do anything? > [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. Again, I'm confused. From our perspective, using the XXE_ADDON_PATH variable is the automatic method--I put the changed config files there, and everyone's office installations find them automatically the next time they open a file with XXE. If I use the add-on manager, then every time I make a change, I have to tell everyone to manually update their installation of XXE using the add-on manager. So the XXE_ADDON_PATH method is easier for everyone. > [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. I'll look into this, but looking at the instructions, I honestly don't think our IT folks are going to buy into it. Mike Maxwell -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
