Win a copy of Pipeline as Code this week in the Cloud/Virtualization forum!
  • 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 ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Bear Bibeault
  • Rob Spoor
  • Henry Wong
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Frits Walraven
  • Himai Minh
  • Jj Roberts

Doubt on the level of lock and concurency

Ranch Hand
Posts: 208
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Suppose a CMP entity bean called EntityBeanA contains a map and a
method called modifyMapElement() which has transaction attribute
of 'require'. If a method X()--which is already in a trasaction--of
another stateless session bean invokes method modifyMapElement() to
modify an element in the map, until the transaction has been either
commited or rollbacked what is being locked in the entity bean to
prevent data inconsistency (eg. prevent others from reading the
content of the map) ? Is it the EntityBeanA or just the map or
something else? If the answer is EntityBeanA, would that degrade app
eat bricks! HA! And here's another one! And a tiny ad!
SKIP - a book about connecting industrious people with elderly land owners
    Bookmark Topic Watch Topic
  • New Topic