JavaWorld Forums: Very out dated and flawed

IMHO your framework will simply create more problems than it solves and suffers from reinvention of the wheel.

The most shocking one is the fact that you propose using a SQL repository. Isn't using a stored procedure a far more sensible way of doing things? It's not like you can tweak the input params or output params available without a code change so what not just use a stored procedure? This kind of approach encourages people not to leverage what's already available on the database. Using stored procs also means that a DBA can call the stored proc directly and interact like the java code does with no ambiguity.

Also any half decent DBA will be able to monitor the performance of stored procs anyway rendering the concept of the SQL repository completely pointless.

Secondly your implementation of a database connection pool is probably the worst I've seen. Nearly all implementations now implement the java.sql.DataSource interface, so that it is transparent whether or not pooling is done. Jarkta commons DBCP provides all the functionality. The JBoss 4.x implementation provides you useful diagnostic information to warn you if you haven't closed a result set, etc, etc.

Frankly I'm surprised Javaworld editors allowed this article to be published as it lacks any technical merit.

InfoWorld: Modernizing IT

JavaWorld: Solutions for Java Developers