Spring out of the box provides little support for loading property attributes based on environments and/or server contexts. Many projects work around this by creating custom ant builds. With Configleon you can build one war file that can be deployed to every location.

Configleon really shines is in it's ability to cascade the property attributes. This allows the common attributes to be defined in a global file and then overridden at the environment and server context.

If we consider the development of a web application, it typically starts in a local environment. The application will then be deployed to various environments including dev, qa, test, and production. Within a given environment, you may be deploying the same application to different server contexts.

For example, say we are deploying the JMesa example web application to the test environment. But we also have two different versions of the application. One is deployed to mycompany.com/jmesa and the other is deployed to mycompany.com/jmesa2. In this example that same war file can use different properties based on both environment and context. In this example, the environment is test and the server context is jmesa and jmesa2.

Trying to deal with all the property attributes related to the various environments can be a nightmare. Worse yet is when you realize many of the attributes do not change between environments. Keeping the property configuration sane is what Configleon does, and it does it very well!

This application has been road tested for a couple years and I am very happy that it is now open sourced! To learn how to run Configleon for a web application read the WebPropertyConfigurer page. To learn how to run Configleon in a (non-web) application or with integration tests read the ApplicationPropertyConfigurer page. Then be sure to use the groups page if you have any questions or problems. Also, if you like or dislike using Configleon let us know that too. Feel free to drop me a quick message at jeff.johnston.mn@gmail.com if that works better for you. As a young project is great to get all sorts of feedback.

In Other News...

If you are in the need of a dynamic HTML table you might want to try the very popular JMesa project. It is a very mature project and is full of solid features that make working with tabular data in your web application a breeze.