This week's book giveaway is in the Design forum.
We're giving away four copies of Design for the Mind and have Victor S. Yocco on-line!
See this thread for details.
Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Why JMS and not MQBase Java???

 
mahadevan raja
Ranch Hand
Posts: 96
  • Mark post as helpful
  • send pies
  • 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
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • 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
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic