My bible for JPA work is the Java Persistence wikibook. It has a section on unidirectional OneToMany which explains how to do this with a @JoinColumn annotation. In your case, i think you would want: @OneToMany @JoinColumn(name=”TXTHEAD_CODE”) private Set<Text> text; I’ve used a Set rather than a List, because the data itself is not ordered. … Read more
JPA 2.0 supports collections of primitives through the @ElementCollection annotation that you can use in conjunction with the support of java.util.Map collections. Something like this should work: @Entity public class Example { @Id long id; // …. @ElementCollection @MapKeyColumn(name=”name”) @Column(name=”value”) @CollectionTable(name=”example_attributes”, joinColumns=@JoinColumn(name=”example_id”)) Map<String, String> attributes = new HashMap<String, String>(); // maps from attribute name to … Read more
If you are using hibernate as your JPA provider you can use the annotation @OnDelete. This annotation will add to the relation the trigger ON DELETE CASCADE, which delegates the deletion of the children to the database. Example: public class Parent { @Id private long id; } public class Child { @Id private long id; … Read more
For multiple properties validation, you should use class-level constraints. From Bean Validation Sneak Peek part II: custom constraints: Class-level constraints Some of you have expressed concerns about the ability to apply a constraint spanning multiple properties, or to express constraint which depend on several properties. The classical example is address validation. Addresses have intricate rules: … Read more
A query of type MyEntity is going to return MyEntity. You want a query for a Long. CriteriaBuilder qb = entityManager.getCriteriaBuilder(); CriteriaQuery<Long> cq = qb.createQuery(Long.class); cq.select(qb.count(cq.from(MyEntity.class))); cq.where(/*your stuff*/); return entityManager.createQuery(cq).getSingleResult(); Obviously you will want to build up your expression with whatever restrictions and groupings etc you skipped in the example.
If you are using it with Hibernate, you’ll have to explicitly define the annotation CascadeType.DELETE_ORPHAN, which can be used in conjunction with JPA CascadeType.ALL. If you don’t plan to use Hibernate, you’ll have to explicitly first delete the child elements and then delete the main record to avoid any orphan records. execution sequence fetch main … Read more