Download Castor & its 3rd-party products dependencies

Documentation Author(s):
Werner Guttmann

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

Latest Released Version: Castor 1.3.2
Release date:
Release notes - What changed ?

The tarball and zips include all the JARs required by Castor, the docs, and the 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 other than javac.

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

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

All implementation JARs (i.e. not 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 marshaling and unmarshaling to and from XML, data persistence using JDO, and source code generation from an XML Schema instance.

The example web 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, and Weblogic) using the standard deployment method of your web application server.

The JARs in this directory carry a timestamp in their name. Please make sure that you always use the latest JAR file, unless you require a specific version.

For those of you working with Maven 2, please add the following dependency to your POM to include the Spring factory beans for Castor XML with your project:

<dependency>
   <groupId>org.codehaus.castor</groupId>
   <artifactId>spring-xml</artifactId>
   <version>0.8-SNAPSHOT</version>
</dependency>

As we currently provide snapshot releases only for the factory beans, you will have to add the following <repository> element to your POM as well, so that Maven 2 knows about the Codehaus Snapshot repository when trying to resolve and download dependencies.

<repository>
    <id>codehaus-snapshots</id>
    <name>Maven Codehaus Snapshots</name>
    <url>http://snapshots.maven.codehaus.org/maven2/</url>
</repository>

The JARs in this directory carry a timestamp in their name. Please make sure that you always use the latest JAR file, unless you require a specific version.

For those of you working with Maven 2, please add the following dependency to your POM to include the Spring ORM package for Castor JDO with your project:

<dependency>
   <groupId>org.codehaus.castor</groupId>
   <artifactId>spring-orm</artifactId>
   <version>RC2-SNAPSHOT</version>
</dependency>

As we currently provide snapshot releases only for the factory beans, you will have to add the following <repository> element to your POM as well, so that Maven 2 knows about the Codehaus Snapshot repository when trying to resolve and download dependencies.

<repository>
    <id>codehaus-snapshots</id>
    <name>Maven Codehaus Snapshots</name>
    <url>http://snapshots.maven.codehaus.org/maven2/</url>
</repository>

You may be able to find some past releases on the HTTP Server:

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://svn.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. For details, please see dependencies.