Introducing Spring Migration Analyzer |
|
It's my pleasure to announce that we've released the first milestone of Spring Migration Analyzer (SMA), a command-line utility that analyzes enterprise Java applications and produces a report describing the application and how it can be migrated to Spring.
Why migrate an application to Spring?
We see two main reasons when people choose to use Spring. Firstly, Spring offers the greatest range of deployment options including cloud and PaaS, allowing you to deploy your application to lighter-weight runtimes with lower operating costs. Secondly, as Adrian recently explained Spring provides access to a host of technologies that are at the forefront of enterprise Java.
When it comes to considering the migration of an existing application to Spring, it's typically the deployment flexibility that motivates the move as it can significantly reduce the application's operating costs.
Using SMA to analyze an application
To get started with SMA, download the distribution. Once it's downloaded, unzip it:
unzip spring-migration-analyzer-1.0.0.M1-dist.zip
With JAVA_HOME set, you can then run the migration-analysis script to analyze an application:
./spring-migration-analyzer-1.0.0.M1/bin/migration-analysis.sh ~/dev/apps/my-app.ear
This will produce an HTML report in a directory named my-app.ear in the current working directory. The report describes the application and offers guidance on migrating it to Spring.
In addition to the migration guidance, the report provides details of things like API usage, EJBs and deployment descriptors that need to be taken into consideration when migrating the application.
Learning more
To learn more about SMA, please refer to the user guide. You may also be interested in the project on GitHub. If you find a bug or have an improvement that you'd like to see, please let us know by opening an issue.
Similar Posts
- Today, Portability Matters More Than Ever
- Countdown to Grails 2.0: Database Migrations
- Upgrading Maven integration for SpringSource Tool Suite 2.8.0
- First Eclipse Gemini Blueprint Milestone Ships
- Git Migration
همس العراق says:
Added on November 27th, 2012 at 4:14 amthanks vry mach
Colin says:
Added on November 28th, 2012 at 1:54 amThat's pretty cool and something I have been thinking of recently as well! There are still many legacy java apps based on EJB's which are holding companies back.
I also thought of how one could "automatically" transform older EJB's to Spring services instead of having to do this manually. Any thoughts/plans on that?
I'll download the analyser and give it a go!
Andy Wilkinson (blog author) says:
Added on November 28th, 2012 at 2:02 amI've given automatic conversion some thought. It would certainly be possible to do some of the work automatically, but I'm not sure that it'd ever be able to get all the way there. I think it comes down to whether or not the automatic part-of-the-way-there transformation would provide a useful foundation for a manual transformation.