Hi Olaf, Did you have a look at our new Listener concept on the PersistenceBroker API? You don't have to implement callbacks on all entity classes, but can write a single Listener component that is registered to a PersistenceBroker. IMHO your Observer problem can solved much easier with this new concept.
have a look at PB.addListener(PersistenceBrokerListener listener) cheers, Thomas Olaf Geibig wrote: > Hello, > > As I mentioned in an earlier post, I'm working on observer/observable > solution to notify clients of changes on persistent objects. I wanted to > put the observer notification call in the afterStore() method of the > PersistenceAware interface implementation of a persistent object. But I > ran into a problem. > > When doing this on an updated object with lots of references to other > tables. The observer notification in the afterStore() method was > executed *before* the whole update transaction was commited, so the > clients did't get the updated objects. I guess the afterStore() method > is called directly after this particular object is stored but is not > waiting for dependent objects to be stored. > > To get around this I thought of creating a thread which is waiting until > the transaction is committed by monitoring the state of the lock of the > updated object. But I couldn't figure out how to do this... I played > around with the LockManager but nothing worked. > > Any Ideas???? > > /olaf > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
