From: Joern T. <joe...@go...> - 2010-08-18 20:58:17
|
On Wed, Aug 18, 2010 at 8:42 PM, Dannes Wessels <da...@ex...> wrote: >> > (4) Saxon >> > It became clear that we have some issues with the newest saxon jar >> > files. In >> > november I found out about a work around, i'd like to propose to follow >> > the >> > work around: install saxon in lib/user [for this we have already an >> > excellent download task], remove all lib/endorsed/saxon*jar files. If >> > we >> > decide to install saxon into the exist-db distribution [adam] this >> > download >> > code can be removed. >> >> Would be nice to have a decision here > > Saxon must be under endorsed.. for sure, but the current version has a bug. > So in the mean time I;d like to propose to put it under lib/user , if mr kay > fixes the issue we'll revert. > I had problems with starting betterforms with the newest Saxon version, > there is a deep dependacy between bf and saxon? Yes, i know Saxon is in endorsed and we rely on this now (not bundling our own any more) I fear you mean saxon 9.2 don't you? I just spend 3 hours on Monday to make our code run with 9.1.0.8 which (due to my last info) is the current vesion used in eXist. We still used 9.0. If i'd known that you want to switch quickly to 9.2 i had not done that upgrade to 9.1. Bit unhappy about that but anyway - must be done one day anyway. Please let me know when the upgrade to 9.2 comes. And yes, we have deep dependency on Saxon as its the XPath engine we use and all of the XPath 2, XForms and custom functions are implemented using Saxon so changes here are the most critical issue in a tight integration of eXist and betterFORM. We should coordinate on version upgrades in time to avoid breaking code. > D. > -- > eXist-db Native XML Database - http://exist-db.org > Join us on linked-in: http://www.linkedin.com/groups?gid=35624 > |