Download Castor & dependencies to 3rd-party products

Documentation Author(s):
Werner Guttmann

Please carefully make yourself familiar with the license model of Castor, available at here.

As of release 0.9.9.1, a new JAR file with the suffix '-commons' has been introduced, holding classes that can be used independend of Castor XML and Castor JDO. With 0.9.9.1 release it only contains Base64Decoder, Base64Encoder, IdentityMap and IdentitySet classes but more (e.g. Castor's cache) will follow with future releases. As this classes are also required for Castor XML and/or Castor JDO they are also included in the other JARs (XML, JDO) that require them. Therefore you don't need to change your class path if it includes one of the other Castor JARs (XML, JDO). Its only intention is to provide you with a small JAR containing classes that are commonly needed by applications even if they do not need Castor's XML and/or JDO part.

and

The tarball and zips includes all the JARs required by Castor, the docs and API JavaDocs. To fully install Castor, simply extract all the JARs into your classpath.

The SVN snapshot includes additional JARs required to build Castor. It is self sufficient and does not require any external components, except for javac.

The documentation set includes JavaDocs for the API and JavaDocs for the full source code, including class usage. A small documentation set without the full source JavaDocs is available in the tarball and zips.

All the JARs included with Castor and used for building Castor are available for distribution free of charge, subject to the respective license agreements.

All implementation JARs (i.e. non APIs) are available under an open source license and available from our FTP server. Open source licenses in use include Apache (ASF), Exolab, Mozilla (MPL), and public domain. All licenses are fully compatible with each other.

The example JAR includes fully functional samples that demonstrate the use of various features of Castor, including marshalling and unmarshalling to/from XML, data persistence using JDO, source code generation from an XML Schema instance.

The example wep application (in form of a WAR archive) includes fully functional samples that demonstrate the use of Castor from within a standard J2EE web application. The WAR file can be deployed to any J2EE compliant web application container (including amongst others Tomcat, WebSphere, JBoss, Weblogic, etc.) using the standard way of deployment of your web application server.

and

http://dist.codehaus.org/castor/

To obtain the latest SVN version, please use a SVN-enabled client to access our SVN server. Instructions for doing so can be found here.

For those of you behind a firewall with the SVN port non-accessible, please download Castor from the SVN server using the HTTP interface at http://cvs.castor.codehaus.org/viewrep/castor/castor/trunk as provided by FishEye (tm):

JARs required to build Castor and dependencies for various packages are contained in the lib directory. JARs required for distribution are marked with bold text:

and optionally

The last two JAR files are required when using patterns with XML Schema type definitions.

Castor XML is dependent on the latest release of Xerces available from the library directory and Apache Xerces. Other XML parser may be used instead of Xerces, however, Xerces is required to provide the XML serializer package for XML document production.

Castor JDO uses Castor XML for processing the XML mapping file and thus has the same dependency on Xerces as explained above.

In addition applications that rely on Java 1.3 and earlier that use Castor JDO must include jdbc-se2.0.jar or any alternative JAR that includes the javax.sql.DataSource interface.

The JDO examples uses Apache Derby and depends on the JDBC driver provided with the examples archive. This driver is only required for running the samples, and is not required otherwise, especially if you use a different database server.

Castor DSML is dependent on the latest release of Xerces available from the library directory and XML Apache. Other XML parser may be used instead of Xerces, however, Xerces is required to provide the XML serializer package for XML document production.

Castor DSML has two implementations, one that uses JNDI and one that uses the Mozilla Directory SDK. Applications that use the JNDI package (org.exolab.castor.dsml.jndi) are required to include jndi.jar or any alternative JAR that includes the JNDI 1.2 API. Applications that use the Mozilla Directory SDK (org.exolab.castor.dsml.mozilla) are required to include ldapjdk.jar or any alternative JAR that includes version 4.0 of the Mozilla Directory SDK.

We recommend using the Mozilla Directory SDK as the JNDI LDAP service provider and have positive experience using it with OpenLDAP. The JNDI LDAP service provider is included in the ldapsp.jar.