Here's some more details. I'm using OJB from CVS. I just updated today. I user ODMG api, but turn implicit locking off. Here's the behavior I see:
I have a Faculty object with a proxied collection of Trainee objects. I have a web application, so let's say the user chooses a Trainee and clicks Delete. The action does the following, each in a separate ODMG transaction.
- (the Faculty object has previously been retreived and put into the session.)
- get the Trainee object using the OID, delete the trainee (both in one tx)
- get the Faculty object using the OID
I then put the Faculty into the sessions and use its trainee collection to populate a dropdown box of Trainees. What happens is that the deleted trainee continues to appear in the list. Via debugging I can see that the Faculties trainee collection still has the deleted trainee.
It seems that the Faculty object is always gotten from the cache and never from the db, so the Trainee collection is wrong. I have to restart my application server in order for the correct collection to show.
This make so sense to me. Clearly I'm not understanding the cache.
Will
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
