Win a copy of 97 Things Every Java Programmer Should Know this week in the Java in General 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 ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Question From Mikalai Zaikin's material

 
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Folks,
Firstly I want to thank Mikalai Zaikin for his superb material.
Can someone please explain me ..
"
An enterprise bean instance can access resource managers in a transaction ONLY in the enterprise bean's methods in which there is a TRANSACTION CONTEXT available. An entity bean with container-managed persistence can access its persistent state in a transaction ONLY in the enterprise bean's methods in which there is a TRANSACTION CONTEXT available.
"
What can TRANSACTION CONTEXT here mean ???
Thanx in Advance
RUF SCJP 1.4
 
Rancher
Posts: 3618
38
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi, Johny.
This not my material, this was taken from EJB spec.
My understanding of this excerpt is :
1. If you do anything with DB from bean's method - you *must* be in transaction context (somebody has to start transaction before you do anything with DB Connection, for example). Because in case method fails to commit, all your changes of DB should be rolled back as well.
2. About state access. If Bean is not in transaction, it's prohibited to call context.getRollbackOnly() or context.setRollbackOnly, because this makes no sense and will throw an exception -> bean will be removed by container. That's why you must be sure that bean' method is running in transaction, if you call any transaction-related method from EJB's context.
.... and that's why "Supports" transaction attribute can be a REAL PAIN, because there is no way to know for sure in which state (Tx or no Tx) method is running....
Cheers!
 
J Johny Rufus
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanx Mikalai,
So if i am not in a transaction but try to acccess a DB resource...will the code complain in deploy time ???
RUF
 
Mikalai Zaikin
Rancher
Posts: 3618
38
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm afraid, it will complain runtime...
 
J Johny Rufus
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanx Mikalai. I can comprehend.
    Bookmark Topic Watch Topic
  • New Topic