Version Mismatch Exception while saving the object

Choula

Hi,

    

     Can anyone help me out how to resolve the version mismatch issue while saving the object with two different sessions?

The requirment is when any document is created we are updating the metadata with the logged in user session and then with the repostitory session we are applying the acl to the documents. If the we reverse the order then we are getting the version mismatch exception while saving the object. My requirement is i need to first apply acl and then update the metadata so that the r_modify value of the object will be the logged in user name.

Thanks in Advance..

Remo

JorgKrause

Andy Flowers wrote:Are you doing a fetch() to get the latest version after setting the ACL?

I would guess not

Just to add some more information abut the necessity of issueing a fetch.

Each object does have an internal attribute, i_vstamp, which is used to check that applied changes to an object won't be overwritten in a scenario like yours. When issueing a save() call, you'll get an exception like this if the i_vstamp isn't the same any longer as in you cached/instantiated object.

As Andy suggested, a simple fetch() will solve your problem.

Regards

Jørg