Win a copy of Mastering Corda: Blockchain for Java Developers this week in the Cloud/Virtualization 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

MDB acknowledge in CMT, with onMessage() declared NotSupported?

 
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I didn't find nowhere how the acknowledge process of a MDB occurs when we are working with CMT and we declare the onMessage() method NotSupported. Does it occur? When? At the end of the onMessage()? At the beginning of onMessage()? Is it undefined?
Also, is the <acknowledge-mode> tag value going to be considered in this case?
Thank you in advance,
Dani Mazzuca
[ April 05, 2004: Message edited by: Dani Mazzuca ]
 
Author & Gold Digger
Posts: 7617
6
IntelliJ IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I didn't find nowhere how the acknowledge process of a MDB occurs when we are working with CMT and we declare the onMessage() method NotSupported.
The section 15.4.8 of the EJB spec 2.0 states:


Message acknowledgment is automatically handled by the container. If the message-driven bean uses container managed transaction demarcation, message acknowledgment is handled automatically as a part of the transaction commit.


Now, since NotSupported is specified, the container will not execute the onMessage() method within a transaction. The EJB specification does not prescribe how containers should execute methods in an unspecified transaction context (section 17.6.5). The spec only gives some possible techniques that container providers may use. Thus, your question cannot be answered based on the EJB spec only since what happens in such a case is let open to the different implementors.
Not very helpful, but anyway...
 
Then YOU must do the pig's work! Read this tiny ad. READ IT!
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