Win a copy of Node.js Design Patterns: Design and implement production-grade Node.js applications using proven patterns and techniques this week in the Server-Side JavaScript and NodeJS forum!
  • 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
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

is transaction attributes are compulsory for all Component Business methods?

 
Ranch Hand
Posts: 257
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is it compulsory to specify transaction attributes for all Component interface business methods?
even for onMessage() of Message-Driven-bean also need compulsory transaction attribute?
is there like default transaction attribute settings.

In HFE book for stateless session bean example there is no transaction attribute.

Yamini.
 
Cowgirl and Author
Posts: 1589
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Howdy -- the list we have in the book is on page 498, and it looks like this;

Session beans:
- Business methods in the component interface -- (the ones YOU write)
(doesn't matter if it is stateless or stateful)

Entity beans:
- Business methods in the component interface
-- ALL home interface methods written by the bean provider, as well as the remove() method from EJBHome or EJBLocalHome (so that also includes create methods)

Message-driven beans:
- onMessage()

Does that help?

Technically there are no *default* transaction attributes according to the spec! But...there *are* some vendors that provide default transaction attributes. So, it doesn't matter how they get into the DD, but according to the spec, they MUST be there. You might be deploying in an app server that does it for you, however, either through deployment tools that simply add it to the DD, or after the fact. But for the exam, you need to assume that they must be there.

cheers,
Kathy
 
You ridiculous clown, did you think you could get away with it? This is my favorite tiny ad!
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic