# EAC Development Toolkit distribution and package contents

The EAC Development Toolkit is distributed as a set of JAR files bundled with the Deployment Template.

The toolkit consists of three JAR files and depends on two others that are distributed with this package. The following sections describe the JAR files. Details about classes and methods can be found in Javadoc distributed with the EAC Development Toolkit. These JAR files must be on the classpath of any application built using the EAC Development Toolkit.

## eacToolkit.jar

This JAR contains the source and compiled class files for the core EAC Development Toolkit classes. These classes encompass core EAC functionality, from which all component implementations extend. Included are low-level classes that access the EAC's central server via SOAP calls to its Web Service interface as well as higher level objects that wrap logic and data associated with hosts, components, scripts and utilities. In addition, this JAR includes the controller implementation used to load the Toolkit's application configuration file, and to invoke actions based on the configuration and the user's command line input.

## eacComponents.jar

This JAR contains the source and compiled class files for common implementations of Oracle Endeca components. These classes extend core functionality in eacToolkit.jar and implement standard versions of Forge, Dgidx, Dgraph and other components of an Oracle Endeca deployment.

## eacHandlers.jar

This JAR contains the source and compiled class files for parsing application configuration documents. In addition, the EAC Dev Toolkit's application configuration XML document format is defined by an XSD file packaged with this JAR. Finally, the JAR includes files required to register the schema and the toolkit's namespace with Spring, the framework used to load the toolkit's configuration.

## spring.jar

The toolkit uses the Spring framework for configuration management.

## bsh-2.0b4.jar

The toolkit uses BeanShell as the scripting language used by developers to write scripts in their application configuration documents.