• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Devaka Cooray
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Martijn Verburg
  • Frits Walraven
  • Himai Minh

HF EJB page 465 Q8

 
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
For option B, can someone explain what is transaction scoping?
Thanks.
 
Ranch Hand
Posts: 130
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
can you please post the question
tx
Pradeep
 
pradeep arum
Ranch Hand
Posts: 130
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
you know what a scope of a variable mean,i mean the scope in which the variable is valid...that way transaction scoping means the extent of the transaction....here in the option B it says MDB's need not be in a transaction...which is false ...since MDB's are a part of the transactions
hope this helps
tx
Pradeep
 
Ranch Hand
Posts: 275
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The question asks about what is true about container support of MDB's and "B" says the container is NOT required to support scoping (and the answer is not checked, therefore the question suggests that the container IS required to support scoping).
After looking through the spec, I still don't REALLY know what they mean by "transaction scoping".
My first thought was that since, in the case of MDB's, there is no related previous transaction, and there is no related follow-on transaction, the container's job is easier (it doesn't have to suspend, or require new or any of that). But apparently that is NOT transaction scoping.
Would it be true to say that "transaction scoping" includes the tasks that the container performs to support a transaction? In that case, the container would always be required to support transaction scoping.
That's a better question: "is there ever a case where the container is NOT required to support transaction scoping"? If there is no such case, then this is much ado about nothing.
--Dale--
[ April 22, 2004: Message edited by: Dale Seng ]
 
eat bricks! HA! And here's another one! And a tiny ad!
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic