The Register® — Biting the hand that feeds IT

Migrating EJB 2.1 Entity and Session Beans to EJB 3.0

The nuts and bolts

By Deepak Vohra • Get more from this author

Posted in Developer, 25th April 2006 06:02 GMT

Free whitepaper – Ensuring high service levels in cloud computing

Summary

So, to summarise this tutorial:

  • EJB development in EJB 3.0 specification is simplified by replacing abstract bean classes with POJOs.
  • Component and Home interfaces are not required in EJB 3.0.
  • Deployment descriptors are replaced with metadata annotations in the bean class. Familiarity with JDK 5.0 annotations is required to migrate EJB 2.0/2.1 to EJB 3.0.
  • The EntityManager API is used to create and find entity bean instances in EJB 3.0 instead of the create, and finder methods in EJB 2.1.
  • JNDI, which is required to obtain references to resources in EJB 2.1 is replaced with the @Resource, @Inject and @EJB annotations in EJB 3.0 specification.

Deepak Vohra is a Sun Certified Java Programmer and Sun Certified Web Component Developer. Deepak is a Web developer; and has published in XML Journal, WebLogic Developer's Journal and ONJava.com.

Page:

Free whitepaper – The top 5 server monitoring battles

Popular Whitepapers

Don’t Miss

Microsoft Office logoOffice 2010 fights Google with SharePoint bloat

Review Decent upgrade gets out of shape

Ubuntu teaser Ubuntu's Karmic Koala bares fangs at Windows 7

Review Shuttleworthian scrap

AppleChange your views: OS X tags exploited

Mac Secrets Apple windows insider

MicrosoftMicrosoft 'Dallas' muscles Google data crusade

PDC Crunches Red Planet