Appendix 7. Development and Runtime Libraries
Prev |  | Next

## Appendix 7. Development and Runtime Libraries

- `kodo.jar`: Library for development of applications for Kodo JPA/JDO.

- `kodo-runtime.jar`: Library for runtime use of Kodo JPA/JDO.

- `kodo-api.jar`: Published Kodo APIs that can be used for build-time dependency resolution.

- `kodo-wl81manage.jar`: Library required to connect to WebLogic 8.1 with `remotejmxtool`. This jar must be included in the WebLogic system classpath.

- `jca1.0.jar`: Java Connector Architecture, used internally by Kodo. Required for all development and runtime use of Kodo. See http://java.sun.com/j2ee/connector/.

- `jdbc-hsql-1_8_0.jar`: Hypersonic pure-java database engine. It is used as a simple JDBC driver for learning Kodo, but it is not required for general development or runtime use. See http://hsqldb.sourceforge.net/. This jar is a `JDK 1.3` compile which doesn't support `JDK 1.4` and higher features found in the standard distribution.

- `jdbc2_0-stdext.jar`: Standard extensions to the JDBC2 API. Required for all development and runtime use of Kodo, unless JDK version 1.4 or higher is being used (since the library is inlcuded with JDK 1.4). See http://java.sun.com/products/jdbc/.

- `jline.jar`: Console handling utility. Used by the sqlline.jar file. This file is only used for SQL debugging; it never needs to be included for Kodo runtime operations. See Section 4.15, “The SQLLine Utility” for more details. Distributed from http://jline.sourceforge.net.

- `jpa.jar`: Interfaces defined by the Java Persistence Architecture in J2EE 5 standard. Required for all development and runtime use of JPA APIs.

- `jdo.jar`: Interfaces defined by the Java Data Objects standard. Required for all development and runtime use of JDO APIs.

- `jndi.jar`: JNDI interfaces. Required for all development and runtime use of Kodo with JNDI, unless JDK 1.4 or higher is being used. See http://java.sun.com/products/jndi/.

- `jta-spec1_0_1.jar`: JTA interfaces. Required all development and runtime use of Kodo. See http://java.sun.com/products/jta/.

- `sqlline.jar`: Command line utility for executing SQL commands directly against a database. This file is only used for SQL debugging; it never needs to be included for Kodo runtime operations. See Section 4.15, “The SQLLine Utility”.

- `xalan.jar`: Apache implementation of the transformation parts of the Java API for XML Parsing. Any JAXP-compliant implementation can be used in place of `xalan.jar`. If JDK version 1.4 or higher is being used, this file is optional, since JDK 1.4 includes a built-in JAXP-compliant transformer. See http://xml.apache.org/xalan-j/.

- `xercesImpl.jar`: Apache implementation of the Java API for XML Parsing. Any JAXP-compliant implementation can be used in place of `xerces.jar`. If JDK version 1.4 or higher is being used, this file is optional, since JDK 1.4 includes a built-in JAXP-compliant parser. See http://xml.apache.org/xerces-j/.

- `xml-apis.jar`: XML interfaces. Required for Kodo development and runtime, unless JDK 1.4 or higher is being used.

Prev |  | Next
6.4. Migrating from Kodo 3.x to Kodo 4.0 | Home | Appendix 8. Release Notes