• 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 ...
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Paul Clapham
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Piet Souris
  • Carey Brown
  • Stephan van Hulst
  • Frits Walraven
  • fred rosenberger
  • salvin francis

dbt in exceptions + transactions + Session bean (BMT)

Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi ,

I read the following in spec ejb-3_0-fr-spec-ejbcore.pdf page 342

If the client request is associated with transaction T1 and instance is already associated with T2, container suspends T1 and invokes bean method with T2. Container resumes T1 when method (with any associated interceptor methods) completes. This case never happens for stateless session bean or a MDB.

The doubt is
What happens if BMT demarcated session bean starts a new transaction (might not be already associated) when the client invokes bean method and client is associated with transaction ? Can this case happen with stateless session bean ? What exception is thrown to client when SLS bean rolls back the transaction associated with it ? Will the client transaction associated with client also be rolled back and clients recieves TransactionRolledBackException ?

    Bookmark Topic Watch Topic
  • New Topic