Article:		Asynchronous Messaging Made Easy With Spring JMS
Subject:		Conclusion is contradictory
Date:		2006-02-28 02:00:16
From:		gepo
Response to: Conclusion is contradictory
I agree. Introducing another framework only due to JMS boilerplate code (which you easily hide with a fascade) is just not worth it.

Showing messages 1 through 1 of 1.

• Conclusion is contradictory
  2006-02-28 07:45:32  srinip [View]
  
  
  The proposed design may not be the right solution for all the projects out there. But in our project, we had several JMS destinations that needed to be managed in dev, staging, and prod environments and using Spring's JMS template approach worked great for us. We found that using Spring made the design and development very modular and it was easy to create isolated tests. I think Spring is more than just another framework. We are using it in all layers our J2EE application (MVC, JDBC, JNDI, JMS etc) and it works perfectly with the TDD concept.