Hello Sander, I'm about to deprecate the ConfigurationRegistry, which we had introduced some time ago to implement deserialisation magic: https://groups.google.com/d/topic/jooq-user/0z6akCcH0RE/discussion
It is essentially used in two places: - AbstractQuery: All queries call it before execution, such that listeners can provide deserialised queries with a valid "Configuration" (Factory), that holds an open JDBC connection. This can be easily replaced by some simple enhancements to the new ExecuteListener API: http://www.jooq.org/manual/ADVANCED/ExecuteListener/ - Factory's deserialisation: All factories referenced from QueryParts and Records automatically "attach" themselves to a JDBC connection I'm curious about the second "feature". Why was this needed, and how was this useful? Can we do without that? I'm trying to get away from having jOOQ objects "attached" to a Configuration. If I succeed, then jOOQ 3.0 may actually be mostly thread-safe Cheers Lukas
