expojo 1.3.2 released!

exPOJO 1.3.2 has just been released.

exPOJO is a super lightweight framework that provides:

• dependency injection in Java (no XML - say goodbye to Spring forever!) using the easy to use ModelExposer class.
• high productivity persistence using the 'exposed POJO model pattern' to access your objects via Hibernate or JDO.
• an ORM wrapper that helps you to build code that is portable across different ORMs.

Version 1.3.2 adds an exceptionally useful 'auto query resource clean up' class donated by Guido Anzuoni from Object Magic: http://www.objectmagic.org. Using this class to encapsulate returned query collection result you don't need to explicitly clean up the query resources associated with those results. Guido's class 'automagically' cleans up the resources when it is garbage collected. This is great for users of the OpenPersistenceManagerInView pattern. Currently Guido's class works with JDO only.

Version 1.3.2 also adds a new flushChanges method which is great when you need to establish an extremely complex object graph with cyclic references. ORMs occassionally generate FK constraints with such object graphs and the only workaround is to perform piecemeal database commits. The new flushChanges method can be called at various steps during construction of a complex object graph to perform piecemeal database commits, upon return from flushChanges the exPOJO transaction depth is restored to its previous value saving the developer from having to save/restore the transaction depth explicitly.

exPOJO: version 1.3 released!

exPOJO Version 1.3 has recently been released.

It now makes dependency injection even easier to use. Simply configure the ExpojoServletFilter in your web.xml and voila!! Too easy.

For the lovers of the highly productive "exposed POJO domain model" pattern you will find the latest version of POJO irresistable.

Read more and download here.

exPOJO: used in major financial company's core enterprise software

A major provider of financial IT resources based in Sydney, Australia is using exPOJO to provide access to their core enterprise objects in a generic way. A variety of their integral applications use exPOJO to expose their core enterprise objects in a consistent and generic way saving thousands of developer hours whenever a new application needs to be created.

The exposed model was implemented using exPOJOs JPOX/JDO wrapper (a Hibernate wrapper is also available) as their transparent persistence solution. JPOX was chosen because it provides virtually 100% transparent persistence at the domain model level and has a significant performance edge due to its ability to perform build time byte code enhancement instead of relying on much slower run time reflection to do its job. The domain model objects are all pure POJOs without any need for annotations or the need to add extra methods to enable the underlying ORM to function correctly.

All domain models are designed and maintained using the light weight, high productivity, Javelin Modeler/Coder which automatically generates all necessary JPOX meta data files based on the information available in Javelin's UML style class diagrams (Hibernate meta data generation is also supported in Javelin)

If you want to try out persisting your POJOs without the massive learning curve or XML configuration nightmare required by Spring et al then you should give exPOJO a try.

Welcome to exPOJO

This blog has been created as an interim meeting place for developers and users of exPOJO to communicate, share ideas, ask questions etc., We are currently in the process of installing a Java based forum called jForum on the exPOJO website but in the meantime please send all questions and comments to this blog.