V3: Is cascade="lock" legal for collections? docs

bforsythe · **Joined:** Wed Jun 08, 2005 3:12 pm **Posts:** 6

I was getting a lazy init exception, and setting cascade="lock" on the collection seems to have fixed the problem, but the documentation doesn't list this as a valid cascade style. Is this just an oversight in the documentation?

vgiguere · **Posted:** Wed Sep 28, 2005 4:37 pm

I don't mean to be rude, but you should really post your exception stack trace as well as your mapping documents. It would make it a lot easier for us to help you :)

Also, post the code that executes and triggers this laxyInitialization exception.

Thanks.
Vincent.

bforsythe · **Joined:** Wed Jun 08, 2005 3:12 pm **Posts:** 6

But a stack trace, etc is irrelevant. My question is whether cascade="lock" is valid for collections, because the manual doesn't list it as a valid option.

To reiterate, is cascade="lock" valid for collections?

vgiguere · **Posted:** Wed Sep 28, 2005 5:06 pm

Well, you talked about a lazy exception. There might have been a way to find a solution to your problem that excluded making use of non documented cascading events.

But if this is irrelevant to you, that's fine with me.

david · **Posted:** Wed Sep 28, 2005 8:37 pm

Look under cascades.java in the engine package. You will find (depending in the version) the info you are after; eg, code fragment

Code:

      STYLES.put("all", STYLE_ALL);
      STYLES.put("all-delete-orphan", STYLE_ALL_DELETE_ORPHAN);
      STYLES.put("save-update", STYLE_SAVE_UPDATE);
      STYLES.put("create", STYLE_CREATE);
      STYLES.put("merge", STYLE_MERGE);
      STYLES.put("lock", STYLE_LOCK);
      STYLES.put("refresh", STYLE_REFRESH);
      STYLES.put("replicate", STYLE_REPLICATE);
      STYLES.put("evict", STYLE_EVICT);
      STYLES.put("delete", STYLE_DELETE);
      STYLES.put("delete-orphan", STYLE_DELETE_ORPHAN);
      STYLES.put("none", STYLE_NONE);