Free hibernate software for linux

BeanKeeper project was formerly called "Simple Persistence for Java" and is a full featured, powerful object/relational persistence and query library for Java.
Philosophy
Java enterprise software, and according to some, the Java language itself tends to go in the direction of extreme softcoding, or at least, in the direction of additional complexity. Weve seen it happen with the EJB framework, and more recently, the Java Server Faces.
That does not need to be so! Other Java persistence frameworks such as Hibernate, TopLink or pBeans already are catching up to the philosophy of simpleness over "abstractness", however, we think there are more steps that can be taken in this direction.
From a developers point of view, especially in a high-level language such as Java, it is a sane assumption, that I do not have to (do not want to) get into the gory details of storing an object, I do not want to hold the databases hand on how to store my object, I do not want to tell it how to create approriate tables, columns, indexes, how to join tables, how to manage connections, how to allocate disk space, how to optimize queries, etc. I assume a "database" as such, should know how to do that without my help, thats why its called "database".
So the point is, a good library should not get in the programmers way, but adapt to the usage of the programmer, and adapt to patterns commonly used. This is what BeanKeeper tries to do. You dont need to (and you cant even) tell it how to store objects, it simply does. You dont need to specify the schema, relation model, id/key attributes, fetching algorithms, database dialect, or anything like that, you can focus on writing the business logic.
Implementation
So how does all this philosophy stuff translate to a persistence software library? The library is not only supposed to handle all low-level database operations transparently, but also some of the more high-level functions. This must be done in order to enable the developer to concentrate only on writing logic.
Main features:
- Simple usage, which is possible with learning only 3 methods, and reading the tutorial.
- Zero-configuration. Nothing needs to be configured, only the database url is needed for the library to initialize.
- Scalability. The library is capable of distributed operation, from virtually unlimited nodes.
- Relations like references to other objects, Lists, Maps, Sets, Collections are handled 100% transparently by the library.
- Large result sets are automatically paged! Paging is 100% transparent, so a million-record result list can be given directly to the presentation layer, without caring for memory usage and database load!
- Transactions are always serializable. Meaning: during a transaction nothing can influence the result of queries from outside the transaction. This practically means, a programmer does not have to care about other transactions possibly influencing the logic inside his transaction.
- Full (transparent) polymorphism support ensures that (most of the time) the library does not get in the way of the programmer. The model is persisted just in the way the programmer expressed through inheritence, and is recalled with all the attributes of polymorphism.
- A custom, object oriented query language ensures, that no complicated SQL needs to be written.
- Scalar query support enables view-centric, more efficient data recall.
- Real portability between databases. BeanKeeper hides all database specific behaviour from the programmer, like: null value handling, empty strings (oracle), case sensitive and insensitive searches, reserved names, etc. That means, one can switch between database implementations, and can assume that (with the exception of a few documented cases) the software build upon the library will continue to work.
Enhancements:
- All known bugs were fixed.
- Primitive type handling was enhanced, so container types (Set, List, and Map) can now contain boxed primitive types too.
- This also means that JDK5 generics are now handled correctly. List member attribute implementation was corrected, so it preserves ordering and can contain duplicate objects.
- The library was relicensed to the LGPL v3.

Spike Asset Manager (SAM) is an open-source cross-platform framework for probing a system for components and reporting them. It includes a driver file that probes for components commonly found in a LAMPJ stack (Apache, MySQL, PHP, Tomcat, etc).
SAM can find multiple versions that are installed, query the rpm database and indicate whether components are running. Driver files may be edited to search for different components.
SAM can be extended by writing extension plugins (shell, perl, python, java, etc). It can also be extended by changing the code and creating additional directives for the driver file.
The list of components that SAM currently looks for include:
- apache2
- axis
- commons-logging
- hibernate
- java
- jetspeed
- jboss
- log4j
- mysql
- openldap
- openssl
- perl
- php
- python
- spring
- struts
- tomcat
Enhancements:
- This development release adds a Web server.
- There is now an AJAX enabled Web client to perform what was previously done via command line.
- This allows a common interface (across operating systems) as well as local and remote administration. AJAX is made possible with integration through MochiKit and JSON.
- The Web site has also moved to the SpikeSource developer Web site.

Mr. Persister is a simple, small, object relational mapping API capable of reading Java objects from, and writing Java objects to relational databases. It was first released july 2004.
Main features:
- Fast! (Faster than Hibernate)
- Read objects of any size in just 3-5 lines of code.
- Automatic and manual mapping of objects to database tables.
- No config files required.
- SQL as query language.
- Automatic connection and transaction management
- (via DAO commands).
- Automatic connection and transaction management
- (via connection and transaction scoping).
- Automatic SQL generation for most trivial tasks.
- Batch updates of multiple objects.
- Compound primary key support.
- Partial object reading and writing.
- Read Filters.
- Simplifies trivial JDBC tasks.
- Interleave custom JDBC with Mr. Persister operations.
- Fully Pluggable Design.
- Well Tested. 290 unit tests were executed against each supported database.
Enhancements:
- Mr. Persister now uses JDK 5.0.
- Some important bugs have been fixed, and the software now enables annotation-based class-to-database mappings both as an alternative and a supplement to automatic and programmatic mapping.

euCatalogue is a catalogue framework in Java to help you build a generic catalogue structure.
euCatalogue includes an "admin Web interface" to help with constructing the catalogue and a "user Web interface" which allows browsing the catalogue.
Installation:
1. Set up a database on the default port 5432 under the name eucatalogue with user/pass eucatalogue
2. Use "database.sql" file under the "installation" dir to generate the required table structure.
Note:
If You want to change the default database settings, use "hibernate.cfg.xml" under the "installation" dir and place it under "/src/resources" before creating the .war file.
hibernate.connection.url (jdbc:postgresql://localhost:5432/eucatalogue)
hibernate.connection.username (eucatalogue)
hibernate.connection.password (eucatalogue)
hibernate.connection.driver_class (PostgreSQL by default)
dialect (PostgreSQL by default. See Hibernate reference for available dialects)
Do not forget to place the required JDBC driver in the classpath!
Enhancements:
- Support for multiple catalogs was added through the CatalogueElement and CatalogueSpawn interfaces.
- A UUID generator is now used instead of an increment for better handling of multi-user environments.
- Hibernate was updated to 3.2.1 and eupersistence to 2.0.
- Previous database schemas must be deleted and replaced with the new one using the .sql script provided under the "installation" dir.

OpenSubsystemss goal is to provide consistent set of business components that solve particular area of interest such as inventory management, order processing, shopping, email and fax communication, document management, imaging and others.
There are many frameworks and libraries attempting to make life of developers easier. Most of them focus on improving certain technology (EJB) or technical problem such as persistence in Java (Hibernate) or view tier for web applications (Struts).
There are very few that actually give developers fully functional business components that are immediately available to be integrated into their application and solve specific business needs. OpenSubsystems is one of them.
OpenSubsystems is dedicated to providing highest quality products by paying attention to innovative design, carefull implementation and thorough testing while staying true to the spirit of open source.
All our development processes and products are extensively documented and available for review and use to wide audience of business analysts, developers and testers.
Enhancements:
Feature requests
Core
- 1674491Generalize DataFactory interfaces by requiring domain id
- 1674470Simplify DatabaseOperation classes by removing redundant arguments
- 1674438Simplify DatabaseSchema interface/impl for read-only schemas
- 1674289Change license to GPL v2 only for Core
Bugs
Core
- 1674498IOException thrown by FileUtils when directory exists
- 1674495NullPointerException in StringUtils.concat method
- 1674483Servlet preservice method not called when login is required
- 1674420NullPointerException in DatabaseConnectionFactoryImpl class
- 1630270NoSuchElement exception when using XAPool

CSVObjects is a free and open sourced Java based framework for transparently parsing and unmarshalling Comma Separated Value (CSV) files and records into Plain Old Java Objects without the need to code the parsing logic manually.

Instead, the parsing library relies on declarative mapping of CSV fields and data types to Java Bean attributes, via a mapping XML file. This is similar to the manner in which Hibernate provides relational table mapping for Java Beans.

The Framework is built upon Stephen Ostermillers excellent CSV reader/parser classes.

Also, the framework provides convenience Xdoclet support for specifying the CSV to Java mapping in the Java source code itself by using Javadoc markup, thereby reducing the burden on the developer to manually maintain separate configuration files.

Installation:

If you have downloaded the binary file release, then you need to include the
CSVObjects- .jar file in your projects library or classpath, ensure that the dependency libraries are also present in the classpath, and thats it!