I know that this test fails, I added it to show that cascade='all-delete-orphan' is needed in hibernate mappings.
I sent a mail about this test:
using only cascade="all" strategy creates some problems, because an element of
a collection is removed from the db only when the owner is deleted. If an
object is removed from the collection, it's not removed from db.
with delete-orphan, when an object is removed from a collection, it is removed
from the database.
I added a test in the pvm test suite to show this (in ProcessExecutionDbTest).
Setting cascade back to "all-delete-orphan" for variable scopes in execution
fixes the test (in this test, a variable scope is removed from the execution,
but not from the db).
I can fix hibernate mappings if you want.
ah, right. no prob. i thought this already happened.
it would be great if you could go over the collections and see which should be get that mapping.
but feel free to say: do it yourself, as I changed it from right to wrong in the first place :-)