Search

2.2. Application Code

download PDF
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.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.