is there a way to manipulate cascade save/delete/update execution such that these policies can be configured to apply based on runtime context as opposed to being hard coded within the HBM.xml

for example within context 1 i want to cascade save "orders" with their "items" and within another context 2, i do not want to propogate the save. these contexts are determined at runtime.

i see that Interceptor has methods to "intercept" a delete for instance, but can it prevent a delete from happening?

thanks in advance,
kagan

Hibernate version:3.0
Name and version of the database you are using:Oracle10

No, you'd need to use a custom listener to acheive something like that.