## DataNucleus JPA Enhancement with Gradle

Contents

The Java Persistence Application Programming Interface (JPA) is the Java’s specification for bridging the gap between object-oriented domain models and relational database management systems (RDBMS). As JPA is just a standard part of Jakarta EE (formerly Java EE), there exists different implementations, DataNucleus being one of them (besides Hibernate). Note that the official reference implementation for JPA is EclipseLink.

### Enhancement / Weaving

A noteworthy behavior of most JPA providers is to “enhance” the domain JPA classes. This technique, also known as weaving, allows to modify the resulting bytecode of your domain classes, in order to essentially add the following capabilities:

• lazy state initialization
• object dirty state tracking, i.e. the ability to track object updates (including collections mutations), and translate such updates into JPQL DML queries, which are translated into database-specific SQL queries
• automatic bi-directional mapping, i.e., ensuring that both sides of a relationship are set properly
• optionally, performance optimizations

Some providers such as DataNucleus have chosen to require all domain classes to be enhanced before any use. This means that enhancement has to be done beforehand at build time, or at any time between compile time and packaging time.

On the other hand, other JPA providers such as EclipseLink and Hibernate do not make enhancement a mandatory prerequisite, and can do it by default on-the-fly at run-time. They still allow to perform enhancement at build time, but this may not be the default behavior.

Performing bytecode enhancement at build time clearly has a performance benefit over the use of slow proxies or reflection that might be done at run-time.

Hibernate for example provides an hibernate-gradle-plugin for calling its enhancer from Gradle, but DataNucleus supports only Maven for now.

### DataNucleus + Maven

If you make use of both DataNucleus and Maven, enhancing your domain classes is as straightforward as calling the official DataNucleus Maven Plugin in your pom.xml. For example, to have domain classes auto-enhanced after each compilation :

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25   ... org.datanucleus datanucleus-maven-plugin 5.0.2 JPA MyPersistenceUnit ${basedir}/log4j.properties true process-classes enhance ...  ### DataNucleus + Gradle If you use Gradle, then one possible solution is to manually call the DataNucleus Enhancer Ant Task in your build.gradle. Below is an example of such custom Gradle task calling the DataNucleus one:   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26  // define Ant task for DataNucleus Enhancer task datanucleusEnhance(dependsOn: compileJava) { doLast { ant.taskdef( name: 'datanucleusEnhancer', classpath: sourceSets.main.runtimeClasspath.asPath, classname: 'org.datanucleus.enhancer.EnhancerTask' // the below is for DataNucleus Enhancer 3.1.1 //classname : 'org.datanucleus.enhancer.tools.EnhancerTask') // define the entity classes def entityFiles = project.fileTree( dir:sourceSets.main.output.classesDir, include: 'my/domain/**/*.class') // run the DataNucleus Enhancer as an Ant task ant.datanucleusEnhancer( classpath: sourceSets.main.runtimeClasspath.asPath, verbose: project.logger.isDebugEnabled(), api: "JPA") { entityFiles.addToAntBuilder(ant, 'fileset', FileCollection.AntType.FileSet) } } } classes.dependsOn(datanucleusEnhance)  This defines a Gradle task first defining the Ant Task then calling it straight away:  1 2 3 4 5  ❯ ./gradlew :MyApp-Domain:build -x test -x integrationtest ... BUILD SUCCESSFUL in 30s 29 actionable tasks: 27 executed, 1 from cache, 1 up-to-date  It goes without saying, but you need to have the related DataNucleus JARs in your dependencies for this to work. This includes datanucleus-core.jar, datanucleus-api-jpa.jar, and javax.persistence.jar. Optimizing the Gradle Build time One of Gradle’s major strengths is its ability to leverage a build cache, by marking tasks as UP-TO-DATE if their input and output are unchanged. The compileJava task has, among other things, the Java source files as inputs and the compiled class files as outputs. At this point, classes are auto-enhanced after compilation. However, our custom datanucleusEnhance task overrides the compiled class files. This invalidates the compiler cache, thus disabling incremental compilation and requires the compileJava Gradle task to never be skipped. Let’s see how we can further reduce build time by skipping re-running the datanucleusEnhance task when source files have not changed at all. Since the DataNucleus Enhancer modifies and overwrites the class files, we can plug the datanucleusEnhance task execution right after the compileJava one, so the latter sees the enhanced classes as its outputs instead. This way, subsequent builds will run much faster. Code speaks louder than words:   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63  // define Ant task for DataNucleus Enhancer task datanucleusEnhancerTaskDef(dependsOn: compileJava) { inputs.files project.fileTree(dir: "${sourceSets.main.java.srcDirs}", include: 'my/domain/**/*.java') outputs.dir sourceSets.main.output.classesDir doLast { if (!Boolean.getBoolean("datanucleusEnhancerTaskDefRun")) { System.setProperty("datanucleusEnhancerTaskDefRun", "true") ant.taskdef( name: 'datanucleusEnhancer', classpath: sourceSets.main.runtimeClasspath.asPath, classname: 'org.datanucleus.enhancer.EnhancerTask' // the below is for DataNucleus Enhancer 3.1.1 //classname : 'org.datanucleus.enhancer.tools.EnhancerTask' ) } } } task datanucleusEnhance(dependsOn: datanucleusEnhancerTaskDef) { description "Enhance JPA model classes using DataNucleus Enhancer" outputs.dir "${project.buildDir}/dn-enhancer" doLast { if (Boolean.getBoolean("datanucleusEnhancerTaskDefRun")) { // define the entity classes def entityFiles = project.fileTree(dir: sourceSets.main.output.classesDir, include: 'my/domain/**/*.class') // run the DataNucleus Enhancer as an Ant task ant.datanucleusEnhancer( classpath: sourceSets.main.runtimeClasspath.asPath, verbose: project.logger.isDebugEnabled(), api: "JPA") { entityFiles.addToAntBuilder(ant, 'fileset', FileCollection.AntType.FileSet) } new File("${project.buildDir}/dn-enhancer").mkdirs() } } } compileJava.doLast { if (!Boolean.getBoolean("datanucleusEnhancerTaskDefRun")) { System.setProperty("datanucleusEnhancerTaskDefRun", "true") ant.taskdef( name: 'datanucleusEnhancer', classpath: sourceSets.main.runtimeClasspath.asPath, classname: 'org.datanucleus.enhancer.EnhancerTask' // the below is for DataNucleus Enhancer 3.1.1 //classname : 'org.datanucleus.enhancer.tools.EnhancerTask' ) // define the entity classes def entityFiles = project.fileTree(dir: sourceSets.main.output.classesDir, include: 'my/domain/**/*.class') // run the DataNucleus Enhancer as an Ant task ant.datanucleusEnhancer( classpath: sourceSets.main.runtimeClasspath.asPath, verbose: project.logger.isDebugEnabled(), api: "JPA") { entityFiles.addToAntBuilder(ant, 'fileset', FileCollection.AntType.FileSet) } new File("\${project.buildDir}/dn-enhancer").mkdirs() } } classes.dependsOn datanucleusEnhance 

Building the project after the changes above in our build script gives up the following execution time:

 1 2 3 4 5  ❯ ./gradlew :MyApp-Domain:build -x test -x integrationtest ... BUILD SUCCESSFUL in 13s 31 actionable tasks: 18 executed, 1 from cache, 12 up-to-date 

Now notice the build time after re-running the same build command again, with no changes in the Java Domain source files:

 1 2 3 4 5  ❯ ./gradlew :MyApp-Domain:build -x test -x integrationtest ... BUILD SUCCESSFUL in 2s 17 actionable tasks: 17 up-to-date 

### Conclusion

In this blog post, we first recalled a brief definition of what the Java Persistence API is, and what the enhancement technique in JPA means. We then tried to see how to call the DataNucleus JPA Enhancer from a Gradle build script, which is, at this time, not supported officially by folks at DataNucleus.

A possible approach explored here is to define a Gradle Ant Task tied to the official DataNucleus Ant Task under the hood. This solution makes it possible to auto-enhance our domain classes, but has a major drawback in that it invalidates the Gradle compile task output cache. As a consequence, it triggers the execution of both the compile and the enhancer tasks at each build, even when the project source has not been modified.

To further reduce build time, a simple yet powerful solution is to override the compile task outputs, by defining them as the result of the enhancement task execution.

As this is something that might be useful to other Gradle-based projects making use of DataNucleus as their JPA provider, I’m currently working on a simple Open-Source Gradle Plugin, inspired by the official Maven Plugin, which will work exactly as depicted in this article. Stay tuned — the library is coming very soon.