Available in versions: Dev (3.19) | Latest (3.18) | 3.17 | 3.16 | 3.15 | 3.14 | 3.13 | 3.12 | 3.11 | 3.10 | 3.9

Generated POJOs

Applies to ✅ Open Source Edition ✅ Express Edition ✅ Professional Edition ✅ Enterprise Edition

Every table and view in your database will generate a POJO implementation that looks like this:

// JPA annotations can be generated, optionally
@javax.persistence.Entity
@javax.persistence.Table(name = "BOOK", schema = "TEST")
public class Book implements java.io.Serializable

// An interface common to records and pojos can be generated, optionally
, IBook {

    // JSR-303 annotations can be generated, optionally
    @NotNull
    private Integer id;

    @NotNull
    private Integer authorId;

    @NotNull
    @Size(max = 400)
    private String title;

    // Every column generates a getter and a setter
    @Id
    @Column(name = "ID", unique = true, nullable = false, precision = 7)
    @Override
    public Integer getId() {
        return this.id;
    }

    @Override
    public void setId(Integer id) {
        this.id = id;
    }

    // [...]
}

Flags influencing generated POJOs

These flags from the code generation configuration influence generated POJOs:

dateAsTimestamp: This influences all relevant getters and setters
unsignedTypes: This influences all relevant getters and setters
interfaces: If interfaces are generated, POJOs will implement them
immutablePojos: Immutable POJOs have final members and no setters. All members must be passed to the constructor
daos: POJOs are a pre-requisite for DAOs. If DAOs are generated, POJOs are generated as well
jpaAnnotations: JPA annotations are used on generated records (details here)
pojosToString: Whether POJOs should have a generated toString() implementation.
pojosEqualsAndHashCode: Whether POJOs should have generated equals() and hashCode() implementations.
validationAnnotations: JSR-303 validation annotations are used on generated records (details here)