I forgot to mention some things about the code in my previous post.

That class makes some serious assumptions. Big ones. It will only work when running inside a Weblogic J2EE container, using Weblogic pooled database connections, and only when running against an Oracle database. Note the lack of error checking around all the casts and reflection. It wouldn't be too difficult to modify it to use different databases or make it more generic.

Using that class in any other situation won't work. In fact, it will probably blow up in some spectacular ways. Used outside these very specific parameters, it may cause your genitals to shrivel up and make that just-bit-into-a-lemon puckering sound.

Other than that, I'm sure it is rock solid.