Thanks for your reply. It is indeed already filed under issue 879. I am just wondering, why nobody cared very much about that problem ;-) (Priority P3 and Status new for the last seven months), since a cascaded delete operation is required to work by section 3.2.2 of the spec:
"If X is a managed entity, the remove operation causes it to become removed. The remove operation
is cascaded to entities referenced by X, if the relationships from X to these other entities
is annotated with the cascade=REMOVE or cascade=ALL annotation element value."
And it is also used that way in example 1 on page 185 in the spec:
@OneToMany(cascade=ALL, mappedBy=”customer”)
public Set<Order> getOrders() { return orders; }
And therefore I assume the current implementation violates the spec.
Regards Heiko
[Message sent by forum member 'hewagn00' (hewagn00)]
http://forums.java.net/jive/thread.jspa?messageID=206812