Gregory, Just got your mail after I sent the one saying that 0.9.9M1 fixes the problem for me.
Anyway, here is some more detail, hope it helps: I have defined CounterType as read-only in my mapping file. I am referencing it in CounterVar. Now, in CounterVar I want to change the reference to CounterType and persist that new information. I am not trying to change the values in the CounterType object itself, but rather change the CounterType reference in CounterVar. That should be allowed. Some pseudo-code (hopefully illustrates the problem more clearly): - begin transaction - Retrieve the CounterVar object (id=1), cv, in DbLocked mode. This reference the CounterType object with id=1 - Retrieve the CounterType object, ct, (id=3) in DbLocked mode. - cv.setType(ct) - Inside the retrieved CounterVar object set a new CounterType reference - commit transaction I get the exception on the commit. If someone is able to tell me what changed between 0.9.7 and 0.9.9M1 to fix this it would simplify my job. Thanks, Vishal. -----Original Message----- From: Gregory Block [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 13, 2005 2:46 PM To: [email protected] Subject: Re: [castor-dev] Using access="read-only" in the mapping file Ok, it's all a bit random... 1) You're using access="read-only". 2) You're then modifying the CounterType object, which is defined in the castor mapping for the DB as being a dependent object of a read- only object? Please describe what you're doing a little more - because the scenario you're describing, yes, probably does fail. :) Like the other one, this might be a bug, or it might be misuse - I can't tell which. ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] ------------------------------------------------- Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
