• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Problem with EJB Spec

 
Ranch Hand
Posts: 569
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Fig 5 of EJB 2.0 Spec Section 7.6 is the state diagram of stateful session bean(SFSB). It shows the "method ready in TX" state would give ERROR if "non-tx" or "different tx method called".
But the point is, under what condition can a "non-tx" method called in this
state?
What I understand is an SFSB must implements SessionSynchronization
interface in order to get into this "method ready in TX" state . And according to Section 17.4.1, its method must with txn attributes either Required, RequiresNew or Mandatory. That is, must be involved in a txn. So, there would be no business method that can execute without a txn context, and there would be no such "non-tx" method available in this state.
Can anyone explain this contradiction?
 
I'm gonna teach you a lesson! Start by looking at this tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic