• 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
  • Liutauras Vilda
  • Bear Bibeault
  • Junilu Lacar
  • Martin Vashko
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Scott Selikoff
  • salvin francis
  • Piet Souris

HFE , message-driven question

 
Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What�s true about message-driven beans? (Choose all that apply)
A.A message-driven bean has a home interface but no component interface.
B.A client never knows a message-driven bean�s identity.
C.A Client sees a message-driven bean as JavaMail message consumer.
D.The lifetime of a message-driven bean is controlled by the container.

Answer
B,D

My View: There are no clients for message-driven beans, then how can we say "A client never knows a message-driven bean�s identity" ?

Pleas explain
 
Ranch Hand
Posts: 8934
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
MDB instances are the consumers of the JMS messages. So the applications which send those messages are the client. An MDB never knows the client directly but only through the JMS broker; Nor do the client knows who will consume the messages they produce, they just send the message to broker. This is how loose coupling is acheived in Message oriented systems.
 
Paper beats rock. Scissors beats tiny ad.
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!