JBoss 3.2.3 -> 3.2.5 Referential Integrity

[nebodin]

Hi

Im pretty new with all of this so I'm sorry if I'm not making myself clear, I'll do my best.

Basically, I have two CMP 2.x entity beans - lets say they are Customer and Order. Order has a unidirectional relationship to Customer. Lets say I create a Customer and then I create an Order with a reference to that Customer.

Previously I was using 3.2.3, and in that version I could delete ("remove") my Customer without first deleting my Order.

I have just upgraded to 3.2.5 and now I cannot delete my Customer until I have deleted any orders that refer to it.

Does this mean 3.2.5 now supports referential integrity, whereas it was not support in 3.2.3? Or is this just some setting somewhere?

I would appreciate any information anyone could give me or point me to on this subject. I have searched throught the change logs but I don't understand most of it and I don't really know what I am looking for.

If you need any more details on my setup, I'll be happy to provide them - just ask.

[nebodin]

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?

[nebodin]

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?