I know there is a way to load relationships early at runtime, and hibernate suggests we mark all relationships as lazy then eagerly load then at runtime. It seems the same might apply to cascade relationships. However, I have not found any mention of this in the docs. Is there a way to change cascading relationships at runtime?

Thanks
Charlie

I'm not exactly sure what you're asking, Charlie. Could you provide an abstract example of what you're wanting to accomplish?

I've recently run across the same question. Shortly, the answer is no.

But, but ! There is a "nifty workaround" http://forum.hibernate.org/viewtopic.ph ... 28#2312128 :-)

Sure. Let's say I have two classes Document and Content. Document has some meta data, and content stores some information about the content, but really it's just the byte array of the content.

class Document {
@OneToOne( fetch = FetchType.EAGER, cascade = CascadeType.ALL )
@JoinColumn(name="content_id")
Content content;
}

class Content {

Integer id;

Date lastModifiedAt;

User lastModifiedBy;

byte[] contents;

}

Now sometimes I want to commit the changes I make to Content when I saveOrUpdate Document and sometimes I don't. However since I've marked this as CascadeType.ALL it gets commited whenever I commit Document. Is there a way I can at runtime change the cascade settings betwen Document and Content?

My particular problem is that I have a case when I don't want to commit changes the user has made in Content because they've modified something in Document.

Thanks
Charlie

It's impossible, as I said. I already wanted to do this a couple of days ago. Look at the answer tenwit provided me in the thread I opened for this : subject.http://forum.hibernate.org/viewtopic.ph ... 28#2312128