You've decided to switch from EJB to Hibernate for persistence in your J2EE applications, but you don't know what to do with your existing EJB tier. Learn how a few decisions upfront, some simple ground rules, and design patterns can smooth the transition.
by Lara D'Abreo
April 20, 2005
ccording to its Web site, Hibernate is a "powerful, ultra-high performance object/relational persistence and query service for Java." And they're not just blowing smoke. Hibernate is a key player in the movement towards more lightweight designs and is quickly becoming the Java persistence tool of choice. The decision to use Hibernate for new projects is a no-brainer, but for mature applications the choice is not as clear-cut.
If you have a large J2EE project—possibly in production—is migrating your existing homegrown or entity-bean-based solution worth it? Perhaps, it all depends on whether your existing persistence layer is deficient or unable to scale to meet your long-term goals. In some cases, the risk may be high and the costs outweigh the benefits. But if you've decided to go with Hibernate, you can minimize the impact of the change and make the transition—if not painless—at least well structured and predictable with a bit of upfront design.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
ccording to its Web site, 
