jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Müller <thomas.muel...@day.com>
Subject Re: Making Derby an optional dependency
Date Wed, 25 Feb 2009 10:07:00 GMT

> remove the compile-scope Derby dependency from jackrabbit-core


> having Derby included for example in WEB-INF/lib of the
> Jackrabbit webapp is troublesome due to the Derby background threads
> making it difficult to properly un- or redeploy such webapps. A better
> alternative is to have the Derby as a shared container-level library
> (common/lib in Tomcat).

FYI: Tomcat and Glassfish 3 sets most static fields (final or
non-final) to null when unloading a web application. This can cause a
NullPointerException with some databases / libraries. In Tomcat >= 6.0
this behavior can be disabled by setting the system property
to false, however Tomcat may then run out of memory. A known
workaround is to put the database / library in the shared lib


View raw message