Re: [Exist-development] Some thoughts about betterforms @ exist

[Joern T. <joe...@go...>]

On Sun, Aug 15, 2010 at 9:22 PM, Dannes Wessels <da...@ex...> wrote:
> Hi,
> I have some thoughts on what we can improve the betterforms integration:
> (1) Split build and install
> If a rebuild of exist is performed, the betterform scrips actually block
> this action:
>      [xslt] betterFORM is allready installed. Please run 'ant uninstall'
> before installing it again
>      [xslt] Failed to process
> /Users/wessels/Development/eXist-db/Contrib/Betterforms/webapp/WEB-INF/web.xml
> Better is to provide instructions to do this install manually:
> ./build.sh -f extensions/betterform/build.xml install
> ./build.sh -f extensions/betterform/build.xml uninstall

Think this is solved by Wolfgangs change to the build.xml

> (2) Remove jars from  lib/user
> -rw-r--r--  1 wessels  staff  261809 Aug 15 20:37 commons-lang-2.4.jar
> move to lib/optional , remove ancient version from cocoon, start.config
> needs to be updated
> -rw-r--r--  1 wessels  staff  502402 Aug 15 20:37 dwr-2.0.5.jar
> can stay here....

Just to  clarify: we have agreed that libs that are only used by
betterFORM should go to extensions/betterform lib directory. So, if
commons-lang is not used elsewhere in eXist we would move it there.

The same is true for the DWR lib.

> -rw-r--r--  1 wessels  staff  203035 Aug 15 20:37 ehcache-1.6.2.jar
> for this one I need to think what to do (experiment) At least we need to get
> rid of the following message in stdout:
> Aug 15, 2010 9:09:17 PM net.sf.ehcache.Cache <init>
> WARNING: An API change between ehcache-1.1 and ehcache-1.2 results in the
> persistence path being set to
> /Users/wessels/Development/eXist-db/Contrib/Betterforms/tools/jetty/work/Jetty_0_0_0_0_8080_webapp__exist__.8xgt21/cocoon-files/cache-dir/
> when the ehcache-1.1 constructor is used. Please change to the 1.2
> constructor.

This should go away when Cocoon is removed.


> Logging already initialized. Skipping...
> (3) log4j
> In std out there are many messages like
> log4j:ERROR Attempted to append to closed appender named [exist.core].
> This is clearly caused due to a 2nd time initialization of log4j. We must
> think of a way preventing log4j to initialize by the betterform code.

At the  moment we still have our own log4j.xml in WEB-INF. This should
be removed. Please direct us to the right location to add our
debugging.

> (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 - i have conflicting opinions
about that at the moment. The last statement i remember was that Saxon
is in lib/endorsed. If that is changed we need to know about that as
our build relies on XSLT2

> Under all conditions, LICENSE.txt files are required for all jar files (the
> ones that are *in* the exist svn)
yes.

Joern

>
>
> Kind regards
> Dannes
> --
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
>
>
>
>
>
>
>
>