Reputation: 802
I'm in the middle of converting a 10-year-old Java EE application to more modern standards. The next phase of this effort involves replacing my EJB 1.1 code with EJB 3.0 code. I've done a lot of reading up on EJB 3.0. However, there seems to be relatively little information on making the direct jump from 1.1 to 3.0, perhaps because the technology evolved so much between the two releases. Can anyone who has gone through this exercise before offer any advice or pointers to any useful reference material? The plan at the moment is to try and preserve as much as possible in the facades, and just let NetBeans create the new EJB classes automatically from the database schema.
Upvotes: 0
Views: 812
Reputation: 6939
I fear that it's easier and faster to reimplement the application (or at least the parts you cannot leave untouched and still use as a legacy service) from scratch, even though it may be harder to explain to management.
Concerning specific help, Adam Bien speaks a lot of transferring J2EE projects to Java EE (although they are usually 2.x) in his talks and he has a good book on how the design patterns changed between the 2 and how to change your code accordingly, maybe this helps:
http://press.adam-bien.com/real-world-java-ee-patterns-rethinking-best-practices.htm
Upvotes: 1