This case study on migrating the open source web application monitoring and management software, Hyperic, to the Spring Framework and Apache Tomcat was originally delivered by Jennifer Hickey at the 2010 SpringOne 2GX conference. This migration work was done for Hyperic v4.5 release.
Here are some of the advantages cited about this migration:
1. Improved testability
2. Reduced code complexity
3. Improved developer productivity
I’m sure you’ll like this if you’re a Java architect or aspiring to be one and either work on/use these tools/technologies in your project – Spring, EJB, Hibernate, Struts, JMS, JMX, ActiveMQ, JBoss, Tomcat, Ant, Maven.
Here’s a link that describes this migration briefly: http://blog.springsource.com/2010/11/10/hyperic-4-5-released/
You can either download the case study from this link – Hypericv4.5_EJBtoSpring_JBosstoTomcat_Migration, or view it in the below slideshare presentation.
- SpringSource Hyperic Application and Infrastructure Management
- Basic HQ Architecture
- Why migrate?
- How Does Lean Help?
- Project Timeline: Project Evolution Begins
- Planning a Migration
- Factors in Migration Complexity
- Partial vs Full Migration
- M1 Goal: EJBs Converted
- Preliminary Steps
- Dependency Injection
- Application Context Files
- Converted EJB Lookup
- Application Context Instantiation
- Data Access and Transactions with Spring and EJB
- Hibernate with Spring and EJB
- EJB Conversion Checklist
- Struts 1.x And Spring
- M2 Goal: WAR on JBoss
- M3: WAR on Tomcat
- Security Conversion
- Scheduling Conversion
- The Last of EJB and JBoss….
- Final Steps M4: Full Distros
- M4 Tasks
- Demo: Integration Testing with Spring
- M5: Functional Complete Maven
- Project Timeline: 4.5 RC
- Conclusion: Wrapping it Up
- Improved maintainability, testability, and reliability
- Next Steps