Emdros is a corpus query system for storing and searching linguistically annotated text. It is very generic, supporting almost any kind of annotation from almost any linguistic theory. All linguistic levels of analysis are supported, including phonology, morphology, the lexical level, syntax, and discourse. The core libraries act as a middleware layer between a client and an underlying SQL database. MySQL, PostgreSQL, and SQLite are supported.
PhiloLogic is a full-text database engine developed for humanities computing text analysis by the ARTFL Project and the Digital Library Development Center at the University of Chicago. It is optimized for fast searching across very large collections of documents. It currently supports TEI-Lite, TEI XML, and TEI SGML documents.
Run BASIC is a powerful, all-in-one Web programming system and application server, designed to make Web programming easy. Its capabilities include the use of the BASIC scripting language, graphics, XML, SQLite database, Cascading Style Sheets, and more. A help file, a tutorial, and example programs are included. This free edition lets you experiment with the Run BASIC system on a single computer.
SAGU, which is a portuguese acronym for "Sistema Aberto de Gestão Unificada", was originaly designed to automate all of what that happens between a student and their Educational Institution. This relationship happens at the academic, financial and administrative levels, and SAGU has subsystems dedicated to these levels. SAGU can be tailored to fit the needs of any Educational Institution.
Sequoia provides high availability and performance scalability for databases. It is is the continuation of the C-JDBC project. It provides transparent database clustering (partitioning, replication, etc.). It works with any Java application without code modification and with any database engine. It has been successfully tested with Tomcat, JBoss, JOnAS, WebSphere, MySQL, PostgreSQL, Apache Derby, HSQLDB, SAP DB, Oracle, DB2, Sybase, MS SQL Server, Firebird, and more.
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.