Thanks for your message. It got duplicated, I will reply to your other thread, here: https://groups.google.com/forum/#!topic/jooq-user/rV0H-A4IvsM
On Thursday, April 4, 2019 at 3:27:32 PM UTC+2, [email protected] wrote: > > We have been using Jooq for sometime, our strategy is to generate PoJo's > from our Postgres 10 DB and then on occassion where appropriate we extend > those generated classes if we wish to add some additional members not in > the DB, this is quite nice as it means we aurtomatically pick up any new db > columns without having to change the code via the generated Pojo. > However while attempting to upgrade to Jooq 3.11.10 from 3.11.0 , I > noticed a change in behaviour which was introduced in 3.11.6, this has > resulted in the inheritied methods from the Jooq generated class not being > visible anymore as when we map via the DefaultRecordMapper it now uses > Class.getDeclaredMethods in Tools.java as opposed to Class.getMethods which > it used previously, getDeclaredMethods does not return public methods from > the parent class just from the actual class, so we can no longer do a > rec.into the class which is extending the generated class, this would > require some refactoring to get it working and leaves us in a worst place. > > was this a deliberate change , can it be rectified? > > offending line in org.jooq.impl.Tools.java , line 3191 in 3.11.10 > > if (suffix != null) { > try { > Method setter = type.getDeclaredMethod("set" + suffix, > method.getReturnType()); > > // Setter annotation is more relevant > if (setter.getAnnotation(Column.class) == null) > result.add(accessible(setter)); > } > catch (NoSuchMethodException ignore) {} > } > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
