New JSR Proposed: JPA 2.1

Update 01. Feb 2011

akquinet joins the JSR-338 expert group to take active part in developing the JPA 2.1 specification.

A new Java Specification Request JSR-338 has been submitted to extend the Java Persistence API (JPA).

The JSR will address a number of features requested by the community:

  • Improvement of the query language and the criteria API
  • Extending the object-relational mapping (custom types, transformation methods, better schema generation, UUID generator types and more)
  • Dynamic definition of persistence unit and object-relational mapping
  • Read-only entities
  • Methods for dirty detection
  • Support for fetch groups or fetch plans
  • and more …

Linda DeMichiel from Oracle, already spec lead of JPA 2.0 and EJB 2.x, 3.x, is the specification lead of the JPA 2.1 expert group. The JCP review ballot closes end of the month and the expert group will be formed as soon as the JSR is approved.

akquinet has a long history in the area of persisting Java objects and object-relations mapping. Michael Bouschen from akquinet is member of the JPA 2.0 expert group, the JDO expert group(s) and the JDO TCK implementation team at apache.

akquinet is supporting this JSR and plans to join the JPA 2.1 expert group to continue the work on Java Persistence.


[This is the english translation of the german article Wireframe-Tools]

Motivation: Reaching UI agility

One of the main goals of agile development is to improve the reaction to changes. Changing UI is expensive in term of time and resources. Indeed, UI changes do not only impact the UI layer, but may also require not planned features and architectural changes. To avoid too late changes, we propose, to our customers, prototypes of applications, tangible regarding interactions and UI design. Those prototypes are developed early in the development process, and so open discussion about the final UI.
Continue reading