• 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

Why JMS and not MQBase Java???

 
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi all,
i have a major problem,I have implemented JMS in Websphere 4.0.2,The JMS Provider is the IBM MQSeries v5.2.
Everything is working fine.On running the jsp in which i have used the MQSeries classes for JMS,the message is put to the corresponding queue,based on the JNDI references and lookups.Forget it.
Now i have a doubt.Why shud i use this JMS,when i can do the same thing using MQBase Java,even using this i can put or get message into a remote or local queue.
Why shud i go for such a complex procedure of creating a resource reference in AAT,mapping it,and all those stuffs.
I dont understand,
Cud anyone plz explain y JMS is given so much importance.
I know that WAS4.0 follows the J2ee standards,and thus according to the standard,v use JMS,but what is the exact technical reason.
Plz help me.
Thanx in advance.
bye
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Besides the obvious standards issues you point out, the major reason is that only the JMS classes provide the transactional tie into the EJB transaction manager. If you use the base MQ classes your MQ puts and gets will NOT participate in the 2phase commit transaction with your database resources.
Kyle
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic