diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml index 794e6fe168..bbc3913bec 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml @@ -14566,6 +14566,32 @@ public class Book {

The above will generate all jOOQ artefacts for your AUTHOR and BOOK tables.

+ +

How to organise your dependencies

+ +

+ The JPADatabase will use Spring to look up your annotated entities from the classpath. This means that you have to create several modules with a dependency graph that looks like this: +

+ + + +

+ You cannot put your JPA entities in the same module as the one that runs the jOOQ code generator. +

diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml index 7df5f0357f..06416c08ad 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml @@ -14966,6 +14966,32 @@ public class Book {

The above will generate all jOOQ artefacts for your AUTHOR and BOOK tables.

+ +

How to organise your dependencies

+ +

+ The JPADatabase will use Spring to look up your annotated entities from the classpath. This means that you have to create several modules with a dependency graph that looks like this: +

+ + + +

+ You cannot put your JPA entities in the same module as the one that runs the jOOQ code generator. +

diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml index 661f1c91a4..e7b4458d7a 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml @@ -15104,6 +15104,32 @@ public class Book {

The above will generate all jOOQ artefacts for your AUTHOR and BOOK tables.

+ +

How to organise your dependencies

+ +

+ The JPADatabase will use Spring to look up your annotated entities from the classpath. This means that you have to create several modules with a dependency graph that looks like this: +

+ + + +

+ You cannot put your JPA entities in the same module as the one that runs the jOOQ code generator. +

diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml index 484d03a5c8..55278bb05e 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml @@ -16619,6 +16619,32 @@ public class Book {

The above will generate all jOOQ artefacts for your AUTHOR and BOOK tables.

+ +

How to organise your dependencies

+ +

+ The JPADatabase will use Spring to look up your annotated entities from the classpath. This means that you have to create several modules with a dependency graph that looks like this: +

+ + + +

+ You cannot put your JPA entities in the same module as the one that runs the jOOQ code generator. +