OpenXava 4.2.2 released

OpenXava 4.5 released

Data for list and collections is obtained via JPA, before JDBC was used.

Automated Business Logic (ABL) library added.

All new layout architecture (the code that paints the UI). It still in BETA but can be activated with layout.painter in xava.properties.

And many other useful new features and bug fixes.

Support for all strategies of JPA inheritance mapping

This feature has been demanded for long time by the community. Until now only single table per class hierarchy mapping strategy was supported, that is the case where all classes hierarchy is stored in the same table. Since OpenXava 4.5 you can also use joined and table per class mapping strategies.

In this case, you have a table for Shop with ID and NAME column and another for InternetShop with ID, NAME and URL columns.

From now on OpenXava will generate a correct user interface for the above classes.

Data for list and collections is obtained via JPA

Until now OpenXava has used JDBC to get the data for list and collections. It was in this way for historical reasons, specially because the very first version of OpenXava used EJB 1.0 CMP entities for persistence and EJB CMP is too slow and rigid to implement the OpenXava list behavior, so we used JDBC. But now, JPA is rapid and flexible enough to be used for obtaining the list data, so we have written a new JPATabProvider to read the data of the list, and it is the one used by default. This allows us to support all the inheritance JPA types, but also opens many interesting posibilities for the future, such as using DataNucleus instead of Hibernate as JPA engine to access to non-relational databases.

All new layout architecture (the code that paints the UI)

The people from SicFlex, a Dominican company that has developed a complete ERP with OpenXava, have developed a new render engine for OpenXava. This is the more important and complicated part of OpenXava. This new render engine will generate even more complex and beautiful user interfaces for OpenXava applications. It is still in beta and it's disabled by default, but you can activate it with the next entries in xava.properties:

# Layout parser calculate and prepare properties to be renderer.
# This is optional, by default OX uses org.openxava.render.DefaultLayoutParser
layout.parser=org.openxava.web.layout.DefaultLayoutParser
# Layout painter, render all properties in cell forms
# If a valid painter is defined here, view rendering is performed by it.
layout.painter=org.openxava.web.layout.DefaultLayoutPainter