JPA uses opposite paradigms.īe aware that JPA’s field population via reflection and proxies can ignore your init-blocks. In Kotlin you try to make everything immutable and initialized on construction. I think JPA and Kotlin are no good match. As you can read further in the same thread, there is another opinion of another Reddit user (original spelling): The above is an actual opinion about Hibernate shared on Reddit.

Hibernate got it backwards and I would even call it an anti-pattern. Hibernate makes trivial things easier and non-trivial things more complex with dozens of gotchas.Ī proper abstraction layer adds a tiny sacrifice for easy things in order to simplify more complex things. Object-Relational Mapping - difference of opinions After reading this article you’ll have a broader perspective on the eternal hate towards ORMs, especially Hibernate, especially mixed with Kotlin. There are pitfalls which you should be familiar with before writing a single line of code using Kotlin and JPA. It’s hard to know all the stuff in the moment you’ve just started using these two technologies. To do that, let’s create an Application class with a main() method.Kotlin and Hibernate might be confusing, especially for the very beginners. We can see that the default executions are disabled using phase none, and Java-specific executions are bound to compile and test-compile phases.

We need to disable them and enable java-compile and java-test-compile instead to ensure that kotlin-maven-plugin execution will happen before maven-compiler-plugin: But the former has two specific executions that are executed before everything else during the phases: default-compile and default-testCompile. So we should place maven-compiler-plugin after kotlin-maven-plugin. We need to adapt maven-compiler-plugin configuration as we need Kotlin sources to be compiled before Java sources.įrequently, Maven plugins executions happen according to the declaration order. This is nearly the end of the configuration.