[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

transaction puzzle

hi all
  i am new to Ozone community recently. i have install, compile, run the example and see the tut and the doc on the site. it's really a wonderful work in the open-source world!!
  but i am puzzled about the ozone's definition of "transaction". in the "user documentation", it says that "each client side invocation of a proxy method creates a new transaction." and "put the code that should run iside one transaction inside one database object method". it's clear. but in the tut, the instruction followed "The GarageApp.java program" says that "In our example we iterate over a collection of objects. Of course this should be a transaction because we do not want the GarageImpl object to be changed while we are working with it".
thus, according the former definition, in the 'oldtimer' section,

"Vector oldtimers = garage.oldtimers();" is a transaction

"car.name()" and "car.age()" is another two transaction

do i understand right? but according to the latter,how to avoid GarageImp object to be changed during the time between these transaction in "oldtimer" section? i mean if the client-side "oldtimer" section is also a transaction process to avoid that thing?

pardon for my ignorance, thx.

»¶Ó­¹âÁÙ http://www.cmmail.com