Integration - eXist: A NoSQL Database and Application Development Platform - page 366

Library Description

$EXIST_HOME/lib/core/antlr-2.7.7.jar Antlr Parser Generator library.

Dependency of eXist core.

$EXIST_HOME/lib/core/log4j-1.2.17.jar Log4J logging library.

Dependency of eXist core.

$EXIST_HOME/lib/endorsed/xercesImpl-2.11.0.jar Apache Xerces2 XML Parser library.

Dependency of eXist core.

$EXIST_HOME/lib/endorsed/xml-resolver-1.2.jar Apache XML Commons Resolver library.

Dependency of eXist core.

$EXIST_HOME/tools/aspectj/lib/aspectrt-1.7.1.jar AspectJ AOP library.

Dependency of eXist core.

$EXIST_HOME/lib/optional/servlet-api-3.0.jar Java Servlet API.

Dependency a of eXist core.

$EXIST_HOME/conf.xml eXist's configuration file.

$EXIST_HOME/log4j.xml eXist's log4j logging configuration file.

a An accidental requirement of eXist 2.0 and 2.1, which will no longer be needed as a
dependency for embedded operation in future versions.

XML:DB Local API
Unlike the XML:DB Remote API, which sends data back and forth across the net‐
work to eXist using the XML-RPC protocol, the Local API instead talks directly to
eXist's internal Java API through function calls within the same JVM process. It is
relatively trivial to switch your code between the local and remote modes of opera‐
tion of the XML:DB API, so if you want to learn a single API and are unsure of which
to choose or wish to use both local and remote modes, it can be a good choice. In
addition, as the XML:DB API is standardized, you could potentially use it to talk to
other XML document systems as well as eXist.
In addition to the runtime dependencies set out in Table 13-8 , you will also need the
one in Table 13-9 .