Skip to main content

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.

Comments

OMax said…
This comment has been removed by the author.
July 30, 2009 at 6:21 AM
Post a Comment

Popular posts from this blog

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 ...
5 comments
Read more

Welcome to exPOJO

This blog has been created as a meeting place for developers and users of exPOJO to communicate, share ideas, ask questions etc., Please send all questions and comments to this blog.
Post a Comment
Read more

Expojo 2.2 is on its way!

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. ExpojoF...
Post a Comment
Read more