asmhatre
448c383879
Same Customer/Order/OrderItem domain modelled with Hibernate/Spring Data JPA and Spring Data JDBC side by side, both running through a shared StatementLoggingDataSource so SQL-statement counts are directly comparable. 11 tests, 11 captured transcripts, 6 doc chapters. Companion repo for the ankurm.com article on when to drop the ORM.
33 lines
1.5 KiB
XML
33 lines
1.5 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<project xmlns="http://maven.apache.org/POM/4.0.0"
|
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
|
|
<modelVersion>4.0.0</modelVersion>
|
|
|
|
<groupId>com.ankurm</groupId>
|
|
<artifactId>sdjpa4-demo-parent</artifactId>
|
|
<version>1.0.0</version>
|
|
<packaging>pom</packaging>
|
|
<name>sdjpa4-demo</name>
|
|
<description>Companion code for the Spring Data JPA and transaction articles on ankurm.com</description>
|
|
|
|
<!--
|
|
An aggregator only. Each module declares its own spring-boot-starter-parent, deliberately:
|
|
|
|
migration-behavior Spring Boot 4.0.6 / JDK 21: the versions the four published
|
|
migration articles were written and verified against. Upgrading it
|
|
would silently invalidate output those articles quote.
|
|
transactions Spring Boot 4.1.1 / JDK 25, current at the time of writing.
|
|
jdbc-vs-jpa Spring Boot 4.1.1 / JDK 25. Same domain modelled with Spring Data JPA
|
|
and Spring Data JDBC side by side, for the "when to drop the ORM" article.
|
|
|
|
Keeping them apart costs one extra pom and means neither article's evidence rots when the
|
|
other module moves on.
|
|
-->
|
|
<modules>
|
|
<module>migration-behavior</module>
|
|
<module>transactions</module>
|
|
<module>jdbc-vs-jpa</module>
|
|
</modules>
|
|
</project>
|