• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

MDB

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is it true that only in the case of MDB u require the JMS?
:roll:
 
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
MDB are consumer of JMS messages.
Yes, you need a JMS to send and receive JMS messages.
A J2EE server provide one implementation of JMS.
 
Pradeep bhatt
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a Q
Is it possible for non-JMS client to consume the message sent by a JMS client. I am takning about Messaging servers such as MQ SERIES.
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sure, the message producer might send the message to WebSphereMQ/MQSeries using the JMS API while the message consumer would use MQSeries' proprietary API.
 
Pradeep bhatt
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Lasse. You are wonderful as usual. Can you please pass me some documents/links suppporting this. It will be helpful.

Originally posted by Lasse Koskela:
Sure, the message producer might send the message to WebSphereMQ/MQSeries using the JMS API while the message consumer would use MQSeries' proprietary API.

 
Lasse Koskela
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Pradeep, here are some IBM RedBooks:
MQSeries + Java
MQSeries + Smalltalk
 
Ranch Hand
Posts: 2713
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by linuss santoo:
Is it true that only in the case of MDB u require the JMS?
:roll:


In EJB 2.1 MDBs have been extented to support other messaging types beyond just JMS. However, it is true that in EJB 2.0 MDBs could only listen to JMS messages.
Like it has already been alluded to, with the exception of MSMQ, all major MOM products support JMS. Therefore, it is usually not terribly difficult to get JMS running on top of the various MOM products. The only real difficulty exists in integrating these MOM products with your J2EE Server. However, since J2EE 1.3 requires the inclusion of JMS, it is usually unecessary to use external JMS Providers with today's J2EE Servers (there are still a few cases where external JMS Providers make sense).
 
reply
    Bookmark Topic Watch Topic
  • New Topic