From: alex <aly...@ya...> - 2011-08-31 00:09:54
|
Back on July 27: > Am Mittwoch, 27. Juli 2011, 13:54:05 schrieb Torsten Schassan: >>> I installed the latest pre-release (1.4.1 rev 14877) on an XP >>> machine. I started exist manually, calling bin\startup.bat. I >>> uploaded all my data, config, apps etc which worked fine. I >>> stopped the machine once and cannot get it up and running again, >>> it starts with the message below and I cannot access the db >>> anymore. Any hints anyone? >> >> after a lot of testing I found out that I experience the problem >> described yesterday only then if I copy saxon to the lib/endorsed >> folder. (I tried saxon9he.) If I remove Saxon, exist will startup >> normally. Any suggestions to this? > > Saxon should already be present in your installation > (EXIST-HOME/extensions/betterform/src/main/lib/saxon-9.2.1.5.jar). > It is also added to the classpath as we need if for betterFORM. So > to get xslt2 running in eXist you should only have to change > conf.xml. This could be a potentially fatal problem for me; saxon-9.2.1.5 is crippled (no extension functionality, and i'm heavily dependent on java.lang.Math), so i need to use saxon-9.1.0.7 at the latest. Simply replacing saxon-9.2.1.5.jar with those of the working version results in the InvocationTargetException described in July's thread; adding the saxon-9.1.0.7 jars in addition to saxon-9.2.1.5.jar doesn't work either, as eXist seems to perform transforms with 9.2.1.5 and i get errors. Any possible ways around this? --alex. . . . |