EAC4J: Apache Commons Configuration via JNDI
OK, here's a problem we all know:
The JEE spec' dictates that no resources should be accessed from a JEE application other than via a JCA comatible datasources, for example, JDBC or JNDI stores... As in other cases, the spec' writer live in an ideal world: In practice, many applications have a filesystem dependency on some product.home directory whee they read configuration from.
"With EAC4J (External Application Configuration For Java) you can externalize your application’s configuration with Apache Commons Configuration and get a Configuration Object via simple JNDI lookup. The isolated classloader decouples all needed classes and dependencies from your application except by one interface."
In simple words, you get a good decouling between the application and the configuration, your application is more standard and you can reload the configuration without restarting the application.While at it, you get support for all configuration stores supported by commons-configuration... Pretty good, I think.