• 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
  • Ron McLeod
  • Tim Cooke
Sheriffs:
  • Devaka Cooray
  • paul wheaton
  • Mark Herschberg
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Frits Walraven
  • Jj Roberts
Bartenders:
  • Carey Brown
  • salvin francis
  • Piet Souris

"container-transaction" Element Declaration, a confusion!

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The EJB Spec Says;

"The Application Assembler uses the container-transaction elements to declare the transaction attributes."



Valentin Crettaz's cheet sheet Deployment Descriptor, on last page color coding suggests that its 'Deployer' who declares <container-transaction> element and transaction attributes.

Am I overlooking or misinterpretting anything?

Regards
 
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The Application Assembler may define the value of the transaction attributes for the methods of the home and component interfaces of the enterprise beans that require container-managed transaction demarcation. It is, however, usually either the job of the Bean Provider or Deployer to ensure that these attributes are set.
 
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well lets face it, some of these role boundaries are fuzzy, just as the roles are somewhat artificial.

The Bean Provider knows and can relate the transaction attributes that the supplied beans can support. The Bean provider may not know which attributes are necessary in each of the targeted applications, and which ones are supported in the operational environment.

The Application Assembler knows which transaction attributes are necessary to fullfil the requirements of the application. The Application Assembler may not know which resources in the operational environment support certain transaction attributes.

The Deployer knows which resources in the operational environment support certain transaction attributes.

So the Bean Provider specifies the beans capability, the application assembler narrows those capabilities to satisfy the applications requirements, and finally the deployer knows which transaction attributes a resource in the operational environment can support.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic