Why don't you use triggers in hsqldb ? You would not need to plug into OJB this way.
Guillaume Nodet > -----Message d'origine----- > De : Coup, Robert Muir [mailto:[EMAIL PROTECTED] > Envoye : dimanche 30 mai 2004 06:51 > A : OJB Users List > Objet : Intercepting updates and inserts > > > Hi all, > > We're using OJB to interface our application to an online database > (Postgre) as well as an offline database (HSQLDB). I'm in the process of > writing some simple replication code to allow offline updates to be > reconciled when the data is synchronised with the online database. > > What I would like to do is to intercept each update or delete being run > by OJB and log some information about it (statement type, table, user, > time, etc) it to another table. I could make all the persistent objects > implement PersistenceBrokerAware and then do the logging in afterUpdate > and afterDelete, but that isn't a stunningly elegant solution and I was > wondering if there was another place I could hook into which wouldn't > involve making changes to my persistent classes? If not, where would be > the best place to jump into the OJB source to do what I need? > > Thanks again, > > Rob :) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
