Eclipse Community Forums: EclipseLink

Help

Home

Home » Eclipse Projects » EclipseLink » UnitOfWork events

Show: Today's Messages :: Show Polls :: Message Navigator

UnitOfWork events [message #491099]

Tue, 13 October 2009 09:15

Ana Oleski

Messages: 22
Registered: July 2009

Junior Member

Hi,

I'm trying to implement a validity-check on all new objects before the unit of work commits (we have "transient" objects with negative ids that should never be put into a relationship with persistent objects but sometime they are).

I thought I would be easy: register for the preCommitUnitOfWork event and examine every object in unitOfWork.getNewObjectsCloneToOriginal().

This approach turned out to have a problem: I only find the new objects that have been explicitely registered and not those that are persisted by reachability.

I looked some more and found the postCalculateUnitOfWorkChangeSet event, which seems to be a good place to do what I want. Only it doesn't. I still don't find all new objects.

I do find them after the commit (postCommitUnitOfWork event) but this is too late, since the database already contains junk.

Of course we can put a constraint in the database and we probaby will. But it still bugs me. What is the true eclipselink way Razz

to do this?

Thanx,

Ana

Report message to a moderator

Re: UnitOfWork events [message #491185 is a reply to message #491099]

Tue, 13 October 2009 15:05

James Sutherland

Messages: 1939
Registered: July 2009
Location: Ottawa, Canada

Senior Member

The non-registered new objects are contained in unregisteredNewObjects (uow.getUnregisteredNewObjects()), you may be able to find them there. You can also trigger them to be discovered if you call uow.assignSequenceNumbers().

You want to try using the preInsert DescriptorEvent instead.

James : Wiki : Book : Blog : Twitter

Report message to a moderator