Though it’s possible to download Databinder from the links below (and its dependencies from their own sites), we don’t recommend it. Please see the setup guide for detailed start-to-finish instructions using Maven.
This release represents a significant refactor of the Databinder toolkit to allow it to work with any underlying persistence technology. Core functionality now resides in modules like databinder-models, while specific functionality is in databinder-models-hib for Hibernate, or databinder-models-ao for ActiveObjects. The “databinder” dependency that was used through 1.1 is now databinder-app and databinder-app-hib for Hibernate applications.
Migration to the new codebase is fairly straightforward. The first step is to refer to the appropriate new Maven artifact name, databinder-app-hib for most applications. Then update dependencies for your IDE, as there are number of class and page renames to work through. Some changes were made to accomodate the new persistence-agnostic structure, others are there to bundle breaking changes into one release. There are no major conceptual changes. Renames are as follows:
A global search and replace for those terms, followed by an “organize imports” command (or whatever is appropriate for your IDE) to find classes in their new *.hib packages should fix most compilation errors. One change to look out for is that HibernateObjectModel will now return null when initialized with an identifier that doesn’t match any entities, to conform to its existing behavior when initialized with queries or criteria.
This upgrade shouldn’t be considered obligatory for Hibernate applications. The 1.1 line will continue to receive fixes and minor features as users require. Speak up on the forum you need anything.
Although Hibernate models are functionally the same in this release, there is one bonus: the new databinder-valid-hib module uses Hibernate Validator to automatically validate against annotated data classes. The recipe book example demonstrates the new module, which should an easy way to eliminate some code in forms with basic validation needs.
Depends on Wicket 1.3.3 and the latest Hibernate modules, to be obtained directly from the JBoss repository. This is the first Databinder release to rely on non-central repositories. As a result, this release can not itself be housed on the central Maven repository. The templates and examples have been updated to use the Databinder repository, but existing applications will need to add the following to pom.xml:
<repositories>
<repository>
<id>databinder</id>
<name>Databinder repository</name>
<url>http://databinder.net/repo/</url>
</repository>
</repositories>modelChanged() calls to DataForm to prevent stale UI state when clearing or changing model object, and checks model binding on detach (if unbound) so that a manual call after saving an entity is unnecessary.Databinder 1.1 is compatible with Wicket 1.3.0 and improves upon its interface with Hibernate such that an external session and transaction manager, such as Spring, can be use with Databinder’s model and component classes. The runnable DataServer class provides a simple embedded Jetty configuration that can be used in development and production. Several new data-oriented components are available, such as the QueryPanel (contributed by Xavier Hanin) and SourceList components.
The product of eleven months of less-than-backbreaking development, Databinder 1.0 provides a simple and effective path to Web applications running over Wicket 1.2.3 and Hibernate 3.2.