Skip to main content

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.
ExpojoFoundation is the key class that is the foundation of the persistent and TDI (Turbo Dependency Injection) of any Expojo based application.


We'll also be moving the source code to Github to make community contributions much easier.

Stay tuned!

Comments

Post a Comment

Popular posts from this blog

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

Version 2.0.1 Released!

After a long period of happy exPOJO usage on a variety of different projects we saw some room for simplification and improvement and version 2.0.1 is the result of this. We've made some excellent refinements and added some new features: New ModelExposerFactory 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 contai...
Post a Comment
Read more