Hi Lukas: Thanks. I can create my own RecordListenerProvider to resolve this issue. What is the use of serializing Configuration object? Will it not create problem in clustered environment if the serialized configuration is used to interact with database?
Regards, Venkat On Tuesday, 10 September 2013 12:34:24 UTC-4, Lukas Eder wrote: > > Hi Venkat, > > Thanks for the clarification. I see where the problem appears to be. > > - Configuration is Serializable > - DefaultConfiguration serialises only those RecordListenerProviders that > are effectively Serializable as well > - You're probably using the DefaultRecordListenerProvider, which is > Serializable > - The DefaultRecordListenerProvider should be used with Serializable > RecordListeners as it has a non-transient RecordListener reference > > So you have two options: > > 1. Make your own RecordListener Serializable > 2. Create your own, Serializable or non-Serializable > RecordListenerProvider to add to the Configuration > > I feel that this design makes sense, but it probably isn't documented well > enough. I have created #2737 for improved manual and Javadoc documentation: > https://github.com/jOOQ/jOOQ/issues/2737 > > Let me know if you feel there is room for improvement in the above design. > > Hope this helps, > Lukas > > > 2013/9/10 Venkat Sadasivam <venka...@gmail.com <javascript:>> > >> Hi Lukas: >> >> Sorry for not being clear on my question >> >> I have added my own org.jooq.RecordListener (not serializable) >> implementation into org.jooq.Configuration object. While serializing record >> object it throws error because my RecordListener is not serializable which >> can be resolved by implementing Serializable interface into my >> RecordListener class. >> >> Does org.jooq.Configuration object needs to be serialized along with >> Record object? On a clustered environment serializing Configuration object >> might lead to error as Configuration object created on server 1 may not be >> valid on server 2. >> >> Regards, >> Venkat >> >> >> On Tuesday, 10 September 2013 12:10:25 UTC-4, Lukas Eder wrote: >> >>> Hello Venkat, >>> >>> I'm not sure what you feel is missing from AbstractStore. In general, >>> Records should be Serializable just as Configuration. A common use-case in >>> jOOQ is to transmit a Record over the wire, modify it on another machine, >>> returning it to the backend server and immediately store it. All that is >>> needed is an appropriate ConnectionProvider to provide jOOQ with a JDBC >>> Connection when store() is called. Some insight can be seen here: >>> http://www.jooq.org/doc/3.1/**manual/sql-building/** >>> queryparts/serializability/<http://www.jooq.org/doc/3.1/manual/sql-building/queryparts/serializability/> >>> >>> What is the problem you're running into? >>> >>> Cheers >>> Lukas >>> >>> >>> 2013/9/9 Venkat Sadasivam <venka...@gmail.com> >>> >>>> Unable to serialize Record object since >>>> org.jooq.impl.**AbstractStore.configuration >>>> is not a transient. Can you make configuration as transient variable to >>>> allow serializing Record object? >>>> >>>> -- >>>> 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+...@**googlegroups.com. >>>> >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>> >>> -- >> 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+...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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.
