Hey, those that know - I need the all-delete-orphan cascade type for a set ( bidirectional one-to-many ), and when I use this <see below>. It appears to be there, but I'm just not using it rigth. Any ideas? ( thanks in advance )

@OneToMany( cascade = { CascadeType.ALL, org.hibernate.annotations.CascadeType.DELETE_ORPHAN )

I get these two error's:

Type missmatch: cannot convert CascadeType to CascadeType

and

[javac] /home/mike1/Desktop/MyBusinessStuff/STB Technologies LTD/code/Java/Working/HBM/HBM Web UnsafeObjects/WEB-INF/src/com/sas/heartbeatmonitor/businessobjects/Location.java:55: incompatible types
[javac] found : org.hibernate.annotations.CascadeType
[javac] required: javax.persistence.CascadeType
[javac] @OneToMany( cascade = { CascadeType.ALL, org.hibernate.annotations.CascadeType.DELETE_ORPHAN } )
[javac] ^
[javac] 1 error


Operating System:
FreeBSD 5.4

Hibernate version:
3.1alpha1

Name and version of the database you are using:
MySQL 4.1.12

Java Version:
1.5.0-p1

Hi,

You are mixing two enums with similar names:
- javax.persistence.CascadeType
- org.hibernate.annotations.CascadeType

The @OneToMany annotation expects only the first one, so your @OneToMany should read:


To also specify DELET_ORPHAN, I do the following but I'm not sure whether its necessary:


The @Cascade annotation is from the package org.hibernate.annotations.

Regards,
Ronald Wildenberg

public Set<Contact> getContacts(){
return contacts;
}

only returns a set with one object in it - and when I look at the database - i can see that more contacts are associated than just this one. Is there more info I need to specify in the Client class than just:

@OneToMany(fetch=FetchType.EAGER)
@org.hibernate.annotations.Cascade({org.hibernate.annotations.CascadeType.ALL, org.hibernate.annotations.CascadeType.DELETE_ORPHAN } )
public Set<Contact> getContacts(){
return contacts;
}

------------------
and in the Contact class I have
------------------
@ManyToOne
public Client getClient(){
return client;
}
public void setClient(Client client){
this.client = client;
}


again, this should be a bi-directional association - there is many Contacts for each client - but only one client for each contact.

:-(

mike

Well, as far as I can tell your code is correct. You could add a mappedBy="client" to your @OneToMany annotation to specify that client is the owning side of the relation, but that is not strictly necessary.

It appears that the problem has nothing to do with the DELETE_ORPHAN.

the problem was in my querries.

crit.setMaxResults(1);

would only return 1 object for each set. So
Client has a set of Locations ( one location returned)
Location has a set of Devices ( one device returned )

So I'd have a "Client" with 1 "Location", with 1 "Device" returned.

:-(

but - remove the setMaxResults() and it starts returning properly.

My bad.

mike