As part of our infrastructure we have some "legacy" EJB applications. As usual these are slow, hard to test, hard to maintain, etc etc. As a result we'd like to refactor them to use Spring/Hibernate. One of these applications is a proprietary monster that it's easier to throw away and rewrite (one of the few occasions where I will agree to the rewrite over refactor path, it's that bad!!), the other two are prime candidates for refactoring: we own the source and we control their lifecycle.
I hope to post a few more articles on our experiences as we go along, but in the meantime here's some reading on other peoples experiences:
First, lets review EJB's, the why and wherefore..
http://dynamicsemantics.blog-city.com/abriefhistoryofejb.htm
Example with a single entity application:
http://kaksles.org/2007/08/11/how-to-migrate-a-legacy-ejb-application-to-spring-and-hibernate/
High-level overview of the process :
http://kaksles.org/2007/08/11/why-migrate-a-legacy-ejb-application-to-spring-and-hibernate/
Story of migrating a large application:
http://jdj.sys-con.com/read/140097_p.htm
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment