Another option for mapping enumerated values is to use an <code>ObjectTypeConverter</code>. A converter allows for type codes to be used on the database instead of the enum's name, which may be required for legacy data.

Another option for mapping enumerated values is to use an <code>ObjectTypeConverter</code>. A converter allows for type codes to be used on the database instead of the enum's name, which may be required for legacy data.

@Enumerated

Use the @Enumerated annotation to specify whether EclipseLink persistence provider should persist ordinal or String values of enumerated constants if the String value suits your application requirements, or to match an existing database schema:

By default, EclipseLink persistence provider assumes that for a property or field mapped to an enumerated constant, the ordinal value should be persisted. In the @Enumerated Annotation example, below, the ordinal value of EmployeeStatus is written to the database when Employee is persisted.If you want the String value of the enumerated constant persisted, set value to EnumType.STRING.

No

Given the enumerated constants in the Enumerated Constants example, the @Enumerated Annotation example, below, shows how to use the @Enumerated annotation to specify that the String value of SalaryRate should be written to the database when Employee is persisted. By default, the ordinal value of EmployeeStatus is written to the database.

Example: @Enumerated Annotation

For more information, see Section 9.1.21 "Enumerated Annotation" in the JPA Specification.

Legacy Data

Another option for mapping enumerated values is to use an ObjectTypeConverter. A converter allows for type codes to be used on the database instead of the enum's name, which may be required for legacy data.