diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml index d09f10dd06..df704b413b 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml @@ -16330,6 +16330,84 @@ public class CaseInsensitiveOrderProvider implements Comparator { +
+ Annotations + +

+ The code generator supports a set of annotations on generated code, which can be turned on using the following flags. These annotations include: +

+ +
    +
  • JPA annotations: A minimal set of JPA annotations can be generated on POJOs and other artefacts to convey type and metadata information that is available to the code generator. These annotations include: +
      +
      • +
      • +
      • +
      • +
      • +
      • +
      • +
    + While jOOQ generated code cannot really be used as full-fledged entities (use e.g. Hibernate or EclipseLink to generate such entities), this meta information can still be useful as documentation on your generated code. Some of the annotations (e.g. @Column) can be used by the for mapping records to POJOs.
    • +
  • Validation annotations: A set of Bean Validation API annotations can be added to the generated code to convey type information. They include: +
      +
      • +
      • +
    + jOOQ does implement the validation spec, nor does it validate your data, but you can use third-party tools to read the jOOQ-generated validation annotations.
    • +
  • Spring annotations: Some useful Spring annotations can be generated on for better Spring integration. These include: +
      +
    • org.springframework.beans.factory.annotation.Autowired
      • +
    • org.springframework.stereotype.Repository
      • +
    • +
+ +

+ The flags governing the generation of these annotations are: +

+ +

+ XML configuration (standalone and Maven) +

+ + + + + true + true + true + + +]]> + +

+ Programmatic configuration +

+ + + +

+ Gradle configuration +

+ + + + +
+
Java Time Types @@ -17023,14 +17101,14 @@ create.insertInto(MY_TABLE) // as a more concise form of this: create.insertInto(com.example.generated.Tables.MY_TABLE) - .values(com.example.generated.Sequences.MY_SEQUENCE.nextval(), com.example.generated.Routines.myFunction())]]> + .values(com.example.generated.Sequences.MY_SEQUENCE.nextval(), com.example.generated.Routines.myFunction())]]>

Configuring these artefacts

The generation of these artefacts can be turned off. For details, see the .

- +
diff --git a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml index a581269aba..a32ecf6ea6 100644 --- a/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml +++ b/jOOQ-manual/src/main/resources/org/jooq/web/manual-3.11.xml @@ -16511,6 +16511,88 @@ public class CaseInsensitiveOrderProvider implements Comparator {
+
+ Annotations + +

+ The code generator supports a set of annotations on generated code, which can be turned on using the following flags. These annotations include: +

+ +
    +
  • JPA annotations: A minimal set of JPA annotations can be generated on POJOs and other artefacts to convey type and metadata information that is available to the code generator. These annotations include: +
      +
      • +
      • +
      • +
      • +
      • +
    • (JPA 2.1 and later)
      • +
      • +
      • +
    + While jOOQ generated code cannot really be used as full-fledged entities (use e.g. Hibernate or EclipseLink to generate such entities), this meta information can still be useful as documentation on your generated code. Some of the annotations (e.g. @Column) can be used by the for mapping records to POJOs.
    • +
  • Validation annotations: A set of Bean Validation API annotations can be added to the generated code to convey type information. They include: +
      +
      • +
      • +
    + jOOQ does implement the validation spec, nor does it validate your data, but you can use third-party tools to read the jOOQ-generated validation annotations.
    • +
  • Spring annotations: Some useful Spring annotations can be generated on for better Spring integration. These include: +
      +
    • org.springframework.beans.factory.annotation.Autowired
      • +
    • org.springframework.stereotype.Repository
      • +
    • +
+ +

+ The flags governing the generation of these annotations are: +

+ +

+ XML configuration (standalone and Maven) +

+ + + + + true + 2.2 + true + true + + +]]> + +

+ Programmatic configuration +

+ + + +

+ Gradle configuration +

+ + + + +
+
Java Time Types @@ -17206,14 +17288,14 @@ create.insertInto(MY_TABLE) // as a more concise form of this: create.insertInto(com.example.generated.Tables.MY_TABLE) - .values(com.example.generated.Sequences.MY_SEQUENCE.nextval(), com.example.generated.Routines.myFunction())]]> + .values(com.example.generated.Sequences.MY_SEQUENCE.nextval(), com.example.generated.Routines.myFunction())]]>

Configuring these artefacts

The generation of these artefacts can be turned off. For details, see the .

- +
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 9e14f20cfe..c7c0874f2d 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 @@ -16031,6 +16031,84 @@ configuration {
+
+ Annotations + +

+ The code generator supports a set of annotations on generated code, which can be turned on using the following flags. These annotations include: +

+ +
    +
  • JPA annotations: A minimal set of JPA annotations can be generated on POJOs and other artefacts to convey type and metadata information that is available to the code generator. These annotations include: +
      +
      • +
      • +
      • +
      • +
      • +
      • +
      • +
    + While jOOQ generated code cannot really be used as full-fledged entities (use e.g. Hibernate or EclipseLink to generate such entities), this meta information can still be useful as documentation on your generated code. Some of the annotations (e.g. @Column) can be used by the for mapping records to POJOs.
    • +
  • Validation annotations: A set of Bean Validation API annotations can be added to the generated code to convey type information. They include: +
      +
      • +
      • +
    + jOOQ does implement the validation spec, nor does it validate your data, but you can use third-party tools to read the jOOQ-generated validation annotations.
    • +
  • Spring annotations: Some useful Spring annotations can be generated on for better Spring integration. These include: +
      +
    • org.springframework.beans.factory.annotation.Autowired
      • +
    • org.springframework.stereotype.Repository
      • +
    • +
+ +

+ The flags governing the generation of these annotations are: +

+ +

+ XML configuration (standalone and Maven) +

+ + + + + true + true + true + + +]]> + +

+ Programmatic configuration +

+ + + +

+ Gradle configuration +

+ + + + +
+
Java Time Types @@ -16724,14 +16802,14 @@ create.insertInto(MY_TABLE) // as a more concise form of this: create.insertInto(com.example.generated.Tables.MY_TABLE) - .values(com.example.generated.Sequences.MY_SEQUENCE.nextval(), com.example.generated.Routines.myFunction())]]> + .values(com.example.generated.Sequences.MY_SEQUENCE.nextval(), com.example.generated.Routines.myFunction())]]>

Configuring these artefacts

The generation of these artefacts can be turned off. For details, see the .

- +