Expojo is an extremely light weight, blindingly fast, elegant framework that implements transparent, ORM engine independence while providing all the dependency injection you need. Expojo comes complete with interfaces to JDO or Hibernate (others can be added easily) and can be used by any UI framework: Wicket, JSP, JSF etc.,
After you've tried it you'll start asking yourself why you were doing things the hard way for so long...
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 gre…
Expojo 2.2 is almost here
Expojo 2.2 has some very useful enhancements but the main changes are name changes to some key classes which make more sense.
Don't worry, we haven't removed the old classes (yet) so your existing code should work fine.
Some of the name changes are:
ModelExposer > ExpojoContext
This class is automatically bound to the thread processing a HTTP request by the ExpojoFilter. ExpojoContext is readily available anywhere in your code via ExpojoContext.get().
It contains all the Repository and Service components that are registered in ExpojoContextFactory's addComponents method.
ModelExposerFactory > ExpojoContextFactory
This factory can be overridden but most likely the existing implementations will provide what you need.
ExpojoServletContextListener > ExpojoFoundation
This class has not really been a ServletContextListener for a long time (the listening is all done by ExpojoFilter now) so it was time for a name change.
ExpojoFoundation is the …