This topic has not yet been written. The content below is from the topic description.
JaVa ee migRation Migrating Java EE applications is in theory no more difficult than migrating pure web applications. However, the purpose of Java EE specifications is to facilitate the integration of multiple frameworks with diverse functionalities. This means that there will in practice be many mini-migrations involved. We will discuss these more in the JSR migration section. aPPlicationS to Migrate app 1 app 2 app 3 app 4 app 5 pplications a App 1 App 2 App 3 App 4 App 5 ibraries l Jakarta Commons 3.2 Apache etc. ramework f Hibernate 3.1 Hibernate 3.4 Spring 2.1 Oracle DB 10g etc. Red Hat Consulting Strategic Migration Planning Guidewww.jboss.com 7 If proprietary IDEs are used in the development of Java EE applications, these will often have the generated classes extend and implement proprietary classes and interfaces. The JBoss MASS project provides a migration analysis tool called MAT, which scans the application’s source code for proprietary libraries and imports. This provides invaluable information for estimating the amount of work that needs to be done for a Java EE migration. The tool is hosted at http://www. jboss.org/mass/mat.html. JBoss MAT also produces detailed HTML reports covering server configuration, deployed applications, and class dependencies.