Couple of questions:
- Why are you dealing with HornetQ implementation classes? It is generally recommend that you stick with the standard JMS API to avoid issues like this when moving between versions/providers.
- How can we say how your code needs to change when we don't know exactly how your code is written? If you want more details on the implementation I recommend you simply look at the actual implementation. It is available on GitHub.
I am using javaee-api-5.0.1 jar as my javax.jms package. So while upgrading to hornetq 2.4, I am facing challenges while creating topicconnectionfactory.
Please suggest me the best option for hornetq up gradation. As of now, I m using the following.
JMS- 1.1 (In javaee-api-5.0.1.jar)
Please let me know whether it will be better if we use JMS 2.0
At this point all I can tell you is that you shouldn't need to change any of your JMS 1.1 code when upgrading. Both HornetQ 2.0 and 2.4 implement JMS 1.1.
I still don't understand why at certain points you're using HornetQ implementation classes rather than the JMS 1.1 API.