While the author of BSAX-J has not yet come to a final conclusion about the need for a binary XML format, BSAX is his idea of one possible encoding that leverages other XML prior art (SAX events and UTF-8, in particular). It is complete in that it can be used to perform round-trip conversions from textual XML to SAX events to BSAX binary streams, and back to SAX events and textual XML. The test code in the distribution does exactly that for a simple example XML file, and measures the difference in file size (the file is slightly smaller for the BSAX encoding of the sample file) and the difference in read time (the read time is significantly faster for the sample file).
JAM (JavaGen Ant Modules) allows Java/J2EE developers to create robust, test-driven build environments with just a few lines of Ant script. Builds are simplified with a standard set of commands that you customize for your project. The Maven-to-Ant bridge manages classpaths, dependencies, versioning, and resource downloads automatically. JAM modules support JBoss, Tomcat 5, Resin, Oracle OC4J, JUnit, Cactus, XDoclet, CVS, Axis, Castor, JMX EJBs, and Hibernate.
SNAP Platform is a development toolkit that packages into an easy to install solution the the Jikes Java compiler, the SableVM Java-like virtual machine and the GNU Classpath Java-like API, and the Eclipse universal tools platform, plus sample programs with source code and developer documentation.
Nennius is an object-oriented application engine. Although initially intended to be a time and expense tracking tool, it has since been improved upon to support a wide array of data types and relationships. It offers the ability to run multiple, concurrent Web applications from a single Nennius engine. Each Web application is fully customizable and can easily be modified to fit almost any existing business model.
XMLImportDB provides an easy-to-use interface that allows developers to create a baseline database environment that can be embedded in their source code for use in jUnit test cases. The database environment can be described in a separate file in the same package as the tests, in a hard coded string in the test case classes, or in any other location for which a java.io.Reader can be created at runtime.