| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS VS MQ Java API |
« View previous topic :: View next topic » |
| Author |
Message
|
| N |
 Posted: Tue Nov 11, 2008 9:23 pm Post subject: JMS VS MQ Java API |
 |
|
Acolyte
Joined: 21 Jul 2007
Posts: 64
|
HI,
Any1 can tell me pro/cons using JMS over MQ Java API?  |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Nov 12, 2008 1:42 am Post subject: Re: JMS VS MQ Java API |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| N wrote: |
| Any1 can tell me pro/cons using JMS over MQ Java API? |
Most of the posters in the Java section have an opinion! 
It does really depend on what your application is doing, the environment it runs in, the kind of messages you're sending, etc, etc.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Nov 12, 2008 3:33 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| If you are sending messages to/from a non-JMS application then using the base MQI may be more logical. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 12, 2008 4:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
| If you are sending messages to/from a non-JMS application then using the base MQI may be more logical. |
Unless the non-JMS application is using XMS.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| manicminer |
| Posted: Wed Nov 12, 2008 4:51 am Post subject: |
|
|
Disciple
Joined: 11 Jul 2007
Posts: 177
|
Personally I prefer the Java API, but that is mostly because I use / like the PCF support 
JMS is good if you want to talk using a standard API, with the possible option of swapping providers. However in reality this doesn't usually work too well as you nearly always end up having to code to provider specific error conditions.
The JMS layer also provides a level of abstraction away from the MQ api, which can be both a good and a bad thing .
If you want to use MQ specific functionality, or talk with non-java applications that also use MQ specific functionality / API (e.g. not XMS) then I would recommend the Java API.
If you want to talk to other JMS / XMS applications, then use JMS.
If you are starting from scratch, consider what you want to achieve long term, then pick either JMS or Java depending |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
