This post follows the first explanation about why writing a back-to-basic library.
I created the RER library (the name will be explained later). It is a kenai project, you can find here: RER Library, source code will be there soon.
This library will only provides good development principles that will allow you to develop a « good » application.
This library will provide:
- Easy Dao writing based on JPA
- Support for other kind of persistence model (JDO ? iBatis ?)
- Support for writing Entity with Interface / implementation separation
- Easy-to-understand-yet-highly-extensible transaction management
- Best practices in web database-base developments
It won’t provide:
- Complicated stuff and technology you don’t have time to understand anyway
- Aspects, magical dependency injection, bytecode instrumentations, annotations, etc…
- Many dependencies to myriads of other libraries in specific versions incompatible with others.
It consists in:
- A set of interface along with their implementation classes
- Singleton and Factory patterns (yes ! with static methods !)
- Configurable with simple java method calls (yes, calling a method, anyone knows this ?)
It will be compatible with:
- Any OS, Application Server (or not)
- Java version 5
- Any java library – Spring, Gwt, Swing, Guice, Wicket, Google App. Engine, J2EE, J2SE etc… just because it’s only made of simple Java classes !
