Skip to main content


Posted by editor on May 27, 2008 at 5:43 AM PDT

Keeping GUIs and their data models in sync with bindings

We return to the idea of beans binding again today, something we looked at not too long ago, but this time, author Thomas Künneth is taking more of a big-picture view.

In our Feature Article, Binding Beans, Thomas takes a look at two frameworks for binding beans: JGoodies binding, which has been around for a few years, and JSR 295 and its reference implementation. Comparing the two, he writes:

Both JGoodies Binding and Beans Binding are powerful frameworks which significantly ease the development of Swing applications. The incorporation of the Presentation Model pattern helps structuring a program, making it more readable and maintainable. Being in the market for quite a while now, JGoodies Binding has become very mature. Still, Beans Binding makes binding beans a breeze, too. In the long run, it might become the framework of choice, especially if it is included in a future Java version and an application must rely exclusively on core libraries.

In Java Today,
this is the last week for the early draft review of JSR 317, Java Persistence API 2.0, which closes on June 1. "The purpose of the Java Persistence 2.0 specification is to augment the Java Persistence API to include further features requested by the community, including additional object/relational mapping functionality and query language capabilities, a criteria-based query API, and standardization of features currently designated as optional, and to align it with related JSRs that are currently in-process and/on in-plan for the Java EE 6 timeframe."

The MigLayout project is the topic of a recent DevX article by Jacek Furmankiewicz, MigLayout: Easing the Pain of Swing/SWT Layout Management. "This article provides a high-level overview of the MigLayout Swing/SWT layout manager and provides an example to demonstrate its power. While MigLayout is the only layout manager I know of that works across both Swing and SWT (different implementation classes but the same constraints API across both UI toolkits), this article focuses mostly on the Swing implementation."

GNU Classpath developer and blogger Andrew Hughes has some ideas about Sharing Secrets, and how Classpath may follow OpenJDK's lead on the problem. "One interesting issue when writing a runtime class library for Java is how to give implementation packages, whether they be in gnu.* or com.sun.*, specialised access to the core runtime classes like those in java.lang. We ran across this problem again recently with GNU Classpath when trying to write CPStringBuilder."

In today's Weblogs, John Ferguson