Ok... I have been doing some searching and reading and I think this is an example of cascade-delete not working and working.
Unfortunately I couldnt really follow the solutions that were given to other people.
Is there a setting which controls whether or not JBoss uses cascade delete, and in 3.2.3 it was off by default but in 3.2.5 it is on by default? Is that all that is going on here?
Ok I have determined that cascade-delete is not the issue here, i do not want cascade delete on. The exception that I am getting now with 3.2.5 when i try to delete something that will damage referential integrity is a good thing - I am only interested in why I wasn't getting it before, i.e. was it a bug and it will never work in previous version, or is it a setting that is now on by default?