• 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
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Container Managed or Bean Managed

 
Ranch Hand
Posts: 176
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The BluePrints book say Entity Beans must use CMT (Container Managed Transactions) where as Sessions Beans can use Container Managed or Bean Managed. Is that a rule or just a norm ? Will the EJB Container throw an error during deployment ?
 
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I would like to know too, I must agree these things are pretty confusing.
Thanks
 
Madhu Juneja
Ranch Hand
Posts: 176
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Section 11.6.1 page 177 of EJB Spec 1.1 says :

Note that only Session Beans can be used with bean managed transaction demarcation. A bean provider is not allowed to provide an Entity Bean with bean-managed transaction demarcation.

My question is what was reason behind such a design ? When persistance of Entity bean can be bean-managed why not transaction management be bean-managed ?
reply
    Bookmark Topic Watch Topic
  • New Topic