Thank for your enquiry and for illustrating your use-case
You could override the JavaGenerator.newJavaWriter() method and return a
JavaWriter that is initialised with @formatter:off. Then override also
JavaWriter.beforeClose() and generate @formatter:on in that method. This
way, you can add these markers to all generated jOOQ classes.
Of course, post processing might be easier (e.g. when using Maven to
generate code) and more forwards compatible, so I'd recommend that if
DefaultRecordMapper already supports classes annotated with @java.beans.ConstructorProperties
(ImmutablePOJOMapperWithConstructorProperties) to map record's fields to
constructor parameters by *name*, rather than by *position*. But using the
said annotation is somewhat obsolete approach on modern (1.8+) JVMs where
the information about parameter names can be compiled into byte code using
-parameters argument to javac.
I'm really interested in supporting this use case, and wondering if this
may be useful for community at large (happy to contribute a patch in such
If Lukas or one of the other core committers can recommend the best
approach of "hacking" this into DefaultRecordMapper I will appreciate it.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].