Hello Sander > Great! Could you give a bit more information on how serialization is > going to work in 1.5.7? Are you going to make Factory serializable, > thereby making everyting that's derived from it serializable?
I'm still working on the details of serialisability in jOOQ. I have come to find it essential that every jOOQ object has access to a org.jooq.Configuration with an underlying java.sql.Connection. This is important for advanced data types in some RDBMS, as well as for a lot of future improvements / bug fixes. So I'm adding a common interface org.jooq.Attachable, which will be extended by the two main top level types in jOOQ: - org.jooq.Store: for data containers like Record, etc - org.jooq.QueryPart: for unexecuted query elements See the trunk version here: http://jooq.svn.sourceforge.net/viewvc/jooq/jOOQ/src/org/jooq/Attachable.java?view=markup The only reference that is going to be transient in jOOQ 1.5.7 is a Configuration's reference to a java.sql.Connection. In order to execute an org.jooq.Query after serialisation/deserialisation, you will have to re-attach it to a Configuration (= Factory), so it can be executed in the context of that Configuration. In short: Your use case should be working out with version jOOQ 1.5.7 > This would really make > things a lot easier in web environments like Wicket. I'm curious about the details of that. How do you integrate jOOQ with Wicket? If I know more about your use case, I could anticipate other issues that might arise... Cheers Lukas
