2013/9/10 Venkat Sadasivam <venkatsa...@gmail.com> > Hi Lukas: > > Thanks. I can create my own RecordListenerProvider to resolve this issue. >
Thanks for the feedback. Good to know. > What is the use of serializing Configuration object? > A Record is usually fetched in the context of such a Configuration. To some users, this context is important even on the receiving end of a transmission over the wire, or when a servlet session is deserialised. This functionality originates from jOOQ 1.x and wasn't reviewed in neither 2.x or 3.x. Do you have an alternative idea in mind to ensure that deserialised records are "attached" to a configuration prior to calling store()? I should've mentioned earlier that if you do not want to produce attached records, there's also Settings.attachRecords, which can be configured: http://www.jooq.org/javadoc/latest/org/jooq/conf/Settings.html#attachRecords > Will it not create problem in clustered environment if the serialized > configuration is used to interact with database? > This depends on the implementations of the various SPI. With the current implementation, I agree, there is some risk of running into similar exceptions as yours. Note that for jOOQ 4.0, a thorough review of Serializability is scheduled: https://github.com/jOOQ/jOOQ/issues/2359 Regards, Lukas -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to jooq-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
