• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

does EJB2.0 supports transaction isolation levels?

 
Ranch Hand
Posts: 257
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
what are transaction isolation levels? does EJB2.0 supports them?

Yamini.
 
Cowgirl and Author
Posts: 1589
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Howdy, no, you don't set isolation levels within EJB 2.0. They are set on the resource itself now, although in EJB 1.0 you WERE able to specify isolation levels in the Deployment Descriptor.

Isolation levels define how protected an operation is from what other operations are doing, and determines how long locks are held, etc. So it is always a tradeoff between performance vs. integrity. If you have NO locks, obviously you have maximum concurrency, but everyone might step on everyone else's transactions and you might corrupt the data, so it really depends on the kinds of operations being done to the database (read vs. write, etc.)

The four isolation levels are often labeled as:

READ UNCOMMITTED (also called "dirty read")

READ COMMITTED

REPEATABLE READ

SERIALIZABLE (has nothing to do with Java "Serializable", but means "one at a time")

But again, you don't need this for the exam!

cheers,
Kathy
 
reply
    Bookmark Topic Watch Topic
  • New Topic