This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
We had our application environment previously developed on WSAD 5 and deployed on WAS 5.
As part of our current project, we are upgrading the infrastructure to RAD 8 and deployed on WAS 7.
Since WSAD 5 and RAD 8 are not compatible, we copied the project structure from original code base and did the build in the new environment from scratch.
For EJB projects, we used the meet-in-middle approach to form the mapping, where we import the required tables, and then match each entity field with database column manually.
Do you have an idea on any other approach which could have been used as the above is time consuming.
That's a big jump! I think you'd be better off rewriting the backend to use JPA. Entity beans end with 2.1 and then have no future. All the effort invested in getting them working isn't an investment in the future. This is still time consuming, but at least when you migrate in the future, you haven't wasted effort.
Unfortunately, there isn't going to be a magic bullet to make this easier. IBM doesn't expect people to jump over two major versions of their product.
Thanks for your response Jeanne, but I don't have option of rewritting/upgrading the current spec.
Am aware that this isn't a smart move but out of my control.
We are currently facing a lot of issue with EJB migration, if we switch first to RAD 7 and then upgrade to version 8.
Would that reduce efforts or lets us say, would it allow me to do a normal migration instead of setting up the whole configuration.