I have two projects. In one, we used the tools to generate the annotations (had been using a prior version of Hibernate), and the graph works. In the second one, collection-based mappings don't work, causing these kinds of errors:

applicationContext.xml]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: org.hibernate.MappingException: Could not determine type for: java.util.Set, for columns: [org.hibernate.mapping.Column(medicalConditions)]
Caused by: javax.persistence.PersistenceException: org.hibernate.MappingException: Could not determine type for: java.util.Set, for columns: [org.hibernate.mapping.Column(medicalConditions)]
at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:217)
at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:114)

I just finished upgrading to the latest releases of the whole stack; nothing changed.

Could not determind type for java.util.Set????

@OneToMany(cascade = { CascadeType.ALL }, fetch = FetchType.EAGER)
@JoinColumn(name="patientId")
public Set<MedicalCondition> getMedicalConditions() {
return medicalConditions;
}

public void setMedicalConditions(Set<MedicalCondition> conditions) {
this.medicalConditions = conditions;
}

Try using a @OneToMany(mappedBy="??????") since this relationship should depend on a foreign key mapped in the MedicalCondition class.

Same error. Thanks for the idea though.

-->> Could not determine type for: java.util.Set, for columns: [org.hibernate.mapping.Column(medicalConditions)]

The Line above might be because the container couldn't recognize the type of MedicalCondition in the Set, so try the following:

@OneToMany(targetEntity=MedicalCondition.class)

Also, check if MedicalCondition has the @Entity And implements the Serializable interface

@Entity
class MedicalCondition implements Serializable{
...

}