I just discovered that cascade delete on a one to many unidirectional CMR doesn't work if a foreign key constraint is set on a DB-level.
My Oracle throws a violation exception. Without fk-constraint everything is fine.
It looks like JBoss tries to delete the parents before the children.
Ok, this might not be a big deal, I can live without FK-constraint
on my Oracle, but it would be nice to have them (in this place things goes live before the admin interfaces are ready ;-) )
Maybe I'm missing something important in my DD (X-Doclet):
* target-cascade-delete = "yes"
* fk-constraint = "yes"