Skip to main content

JPA 2.0 enums with custom values

Let's consider we have this enum



public enum EmpType {

FULL_TIME("e1"), PART_TIME("e2");

private String val;

private EmpType(String val) {

this.val = val;

}

@Override

public String toString() {

return val;

}

}

And the entity



@Entity
@NamedQueries({
@NamedQuery(name="Employee.findByEmployeeType", query="SELECT e FROM Employee e WHERE e.employeeType = ?1")
})

@Access(AccessType.FIELD)

public class Employee implements Serializable {

private static final long serialVersionUID = 1L;

@Id
@GeneratedValue(strategy = GenerationType.AUTO)
private Long id;

@Transient
private EmpType empType;


public Long getId() {

return id;

}


public void setId(Long id) {

this.id = id;

}


public EmpType getEmpType() {

return empType;

}


public void setEmpType(EmpType empType) {

this.empType = empType;

}


@Access(AccessType.PROPERTY)
@Column(name="employee_type")
protected String getEmployeeType() {

return empType.toString();

}


protected void setEmployeeType(String employeeType) {

for ( EmpType empType : EmpType.values() ) {

if ( empType.toString().equals(employeeType)){

this.empType = empType;

}

}

}


@Override
public String toString() {

return " ID : " + id + ", employee type : " + empType;

}


}


Note : Please checkout how i'm using @Access annotations at two different places, they are mandatory.


public class Main {


public static void main(String[] args) {

Main m = new Main();

Employee e = new Employee();

e.setEmpType(EmpType.PART_TIME);

em.persist(e); // assume we are persisting this entity


m.executeQuery(EmpType.PART_TIME);


}


public void executeQuery(EmpType emptType) {

EntityManagerFactory emf = Persistence.createEntityManagerFactory("PrepApp1PU");

EntityManager em = emf.createEntityManager();


Query query = em.createNamedQuery("Employee.findByEmployeeType");

query.setParameter(1, emptType.toString());

List list = query.getResultList();

System.out.println ( list.get(0) );


}


}




the above code will save entity as follows


ID EMPLOYEE_TYPE

1 e2


Also please carefully checkout how i'm searching employees based on enums. Also carefully checkout getEmployeeType(), setEmployeeType method signatures



the executeQuery method will print this

ID : 1, employee type : e2

Comments

MyOnlyBlog said…
This comment has been removed by the author.
MyOnlyBlog said…
This comment has been removed by the author.
MyOnlyBlog said…
Intesar,
you are using the enum as a placeholder for string values. Basicaly enum is used just like any class or interface. You can put your values in an entity class as well.

Popular posts from this blog

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc

Validating CSV Files

What is CsvValidator ?   A Java framework which validates any CSV files something similar to XML validation using XSD. Why should I use this ?   You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference. Why did I write this ?   Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing. What is the license clause ?   GNU GPL v2 Are there any JUnit test cases for me checkout ?  Yes,  source How to integrate in my existing project ? Just add the Jar which can be downloaded from here  CsvValidator.jar  and you are good. Instantiate  CsvValidator c onstructor which takes these 3 arguements          // filename is the the file to be validated and here is a  sample         // list - defines all the fields in the above csv file ( a