Xindice is an open source Native XML Database. It stores and indexes compressed XML documents in order to provide that data to a client application with very little server-side processing overhead. It also provides functionality that is unique to XML data, which can't easily be reproduced by relational databases.
DBPrism is an open source framework to generate dynamic XML from a database. It connects Oracle databases with Apache Cocoon, providing a high performance DBGenerator with functionality such as parallel content aggregation and ESI cache protocol. It also includes a powerlful database oriented CMS built on top of Apache Cocoon2 and DBPrism.
This small tool connects to the P6Spy JDBC logger and displays in real time the queries going to the database. It uses an integrated SQL parser to build statistics on the most accessed tables and columns to enable database index creation. Other information is also gathered and displayed, such as the request time for a single request, for a class of request, and for all the requests. Sorting may be done on these views to detect database problems efficiently.
The JGenerator is a Web server production application that can dynamically combine text, graphics, and sound to build rich Flash content. It is a free alternative to and analog of Macromedia Generator. It supports most of the Macromedia Generator features, uses the same data format and the same set of commands, and emulates its behavior.
X2c is an Xbase compiler that creates executable programs from Xbase source on any Unix or C platform. This is accomplished by creating C source from the Xbase source, compiling, and linking with included Xbase function libraries. Whilst the C source is considered an intermediate stage for X2c, it can be used and developed as any other C source. The X2c dialect of Xbase accepts virtually all statements from Borland (was Ashton-Tate), dBASE III PLUS, Computer Associates (was Nantucket), Clipper (Summer '87), and Microsoft (was Fox Software) FoxBASE (2.1). Selected Foxpro statements are also supported.
jUDO (java Universal Data Objects) speeds up development/maintainence and removes database-vendor dependency for applications using databases. You should use jUDO whenever you don't want to use EJBs. You don't write any database code; you only have to specify the container classes and the interfaces for the models, and then jUDO creates the implementation for you runtime (no source is generated). It derives all info needed from your interfaces method names that follows name-pattern rules. In case you need some special access method, you either add a plugin for this or simply go directly against the database. jUDO is not as configurable and advanced as other much more professional software like Castor, Hibernate, etc., but since jUDO derives the database from your code, there is never a mismatch between code and database.