We've made some excellent refinements and added some new features:
The most notable refinement is that the PersistenceProviderFactory has been renamed to ModelExposerFactory which is extended within your application to become the single object reponsible for producing ModelExposer's when required.
Previously ModelExposers were produced by the ExpojoServletContextListener which unfortunately tied the use of exPOJO to web based applications. Now that ModelExposer's are produced by a separate ModelExposerFactory that is independent of the servlet API exPOJO can be used equally well in web app and traditional Java applications.
Even within web based development there is often the need for background threads running as part of the web app or running as services outside of a servlet container and this recent refinement of the exPOJO design makes it possible to implement exPOJO in both the web app and supporting services using common source code.
Simple Wrapping of method within a transaction context
The basic pattern for using the ModelExposer is as follows:
// Either find a ModelExposer associated with the current context or create
// a new one each time - the choice is yours. The context could be a HTTP
// session or anything you want it to be.
modelExposer = context.getModelExposer();
if ( modelExposer == null )
modelExposer = ModelExposerFactory().get().createModelExposer();
// Inject (attach) the ModelExposer to this thread so that within any
// methods executed by this thread the model exposer is instantly
// accessible without requiring direct injection of individual
// objects via ModelExposer.get()
// Get the PersistenceProvider and begin a transaction
PersistenceProvider pp = modelExposer.getPp();
// Typically call a method to perform work like servicing a HTTP request or
// executing an iteration of a periodic background task
// do something with your model - load objects, navigate along
// relationships etc., populating UI components: pages, forms, fields etc.,
// example of code that may be executed within a method that does the work:
// UI elements, model objects etc., all have access to the repositories and
// services and the methods of the PersistenceProvider by simply calling the
// convenience methods eg.,
// User user = UserRepository.get().findUser(username);
// Order order = OrderService.get().createOrder(customer);
// Commit the transaction
catch (Exception e)
// rollback if required etc.,
// Detach from this thread - as threads are pooled in a servlet container we must
// not leave the model exposer attached to any particular thread after it
// has finished servicing the current http request
In exPOJO 1.x what tended to happen was that this familiar pattern ended up being implemented in multiple places throughout the code. In 2.x a new method in ModelExposer makes it simple to wrap code in such a pattern without having to repeatedly write implementations of the whole pattern. The implementation within ModelExposer can simply be reused, wrapping any doWork() style method that you require. The doWork() style method in ModelExposer is actually called execute() and it supports the passing of parameters if required.