Show Table of Contents
2.2. Application Code
If you are using standard JMS in your application, you will need to make modifications to your source code regarding High Availability (HA) and clustering. Specifically you will need to adjust how your application handles failures and rollbacks. For more information, refer to Section 2.3, “Client-side Failure Handling”.
If you are using JBoss Messaging proprietary features, such as ordering groups, you will need to adapt them to HornetQ equivalent features. Table 2.1, “Implementation class mapping between JBoss Messaging and HornetQ” lists the JBoss Messaging JMS implementation classes and their corresponding HornetQ equivalents.
Table 2.1. Implementation class mapping between JBoss Messaging and HornetQ
| org.jboss.jms.client. Classname | HornetQ Equivalent Classname |
|---|---|
JBossConnectionFactory | org.hornetq.jms.client.HornetQConnectionFactory |
JBossConnection | org.hornetq.jms.client.HornetQConnection |
JBossSession | org.hornetq.jms.client.HornetQSession |
JBossMessageProducer | org.hornetq.jms.client.HornetQMessageProducer |
JBossMessageConsumer | org.hornetq.jms.client.HornetQMessageConsumer |
Note
Unless you have used JBoss Messaging-specific APIs, it is not necessary to explicitly case your JMS objects to specific implementations. You can just use the standard JMS APIs wherever possible.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.