This is again a small JMS configuration stuff we have to do in JBoss 5. There is considerable difference in doing it in JBoss 5 compared to JBoss 4 and don’t expect our old configuration to work well with JBoss 5 without any change. In JBoss 5 they are using JBoss Messaging in place of JBoss MQ. You can read a detailed post on migrating from JBoss 4 to JBoss 5 here.
Upgrading JBoss 4 to JBoss 5 with Java 5 to Java 6
The information presented here comes from an effort to upgrade a Java enterprise application to the most current versions of all of its parts; primarily to get onto Java 6. Its starting system specifications were the following:
GASwerk - Geronimo Application Server Assemblies
GASwerk provides production ready solutions based on proven OpenSource components.
Three server assemblies based on Apache Geronimo Application Server are available. Each of them solving a particular problem.
GASwerk SOA Stack is a powerful feature-rich SOA assembly for agile businesses that want to bring their IT department closer to their business processes. GASwerk SOA provides an Enterprise Service Bus for connectivity and an business process engine to model all the processes.
GASwerk Spring is focused on developer needs. It provides a Spring framework deployment feature. Equipped with GASwerk Spring, your Geronimo Application Server is able to directly deploy Spring Applications to your server.
GASwerk JMS is a Messaging Cluster based on Javas Messaging Service (JMS). It is a powerful, scalable solution for companies where message throughput and reliability is critical.
And of course you could use all the GASwerk pieces together or only parts of the whole stack.
Geb GAS!
JMS provides an elegant solution for overcoming the restrictions you face when developing concurrent applications with EJB. Learn how its asynchronous model and its support for the MessageDrivenBean can enable a client to use EJB asynchronously.