Migrating to EJB 3.0 is a big step towards simplifying the process of developing EJBs, which reduces lots of complexities, time and cost.

Java Developers Desk-EJB 3.0

       

Migrating to EJB 3.0 is a big step towards simplifying the process of developing EJBs, which reduces lots of complexities, time and cost. In spite of being rich featured, developers feel complex working with previous versions of EJB.
 

1. Limitations of EJB 2.1
   Developing EJB before release of EJB 3.0 was not so easy because of some unnecessary steps involved that are usually unused. Some limitations of EJB 2.1 are listed below:
   
   • A set of three source files must be create
   • Creating multiple xml deployment descriptors
   • Implementing several callback methods
   • Throwing several types of exceptions
   • EJB-QL is limited in functionality and difficult to use

 

Read more at:

http://www.javajazzup.com/issue5/page12.shtml

 

Related Tags for Java Developers Desk-EJB 3.0:
c,  com,  io,  version,  ejb,  vi,  developer,  versions,  with,  work,  lex,  feature,  developers,  complex,  e,  it,  rsi,  pe,  dev,  in,  m,  j,  working,  spi,  pi,  s,  rich,  sp,  ee,  at,  k,  mpl,  pre,  develop,  ea,  s,  s,  ri,  th,  fe,  ple,  pl,  pr,  on,  om,  o

More Tutorials from this section

• ajax redefining
• Editor?s Choice -AOP and IoC
• Design Pattern
• October 2007 Issue of Java Jazz up magazine
• Java Developers Desk-EJB 3.0
• Java ME
• Java Around the Globe
• JBoss Seam - Stitching JSF and EJB3
• New Releases
• Struts2
• Tips & Tricks
• Tomahawk Tags
• Java Developers Desk-EJB 3.0
• What is the difference between EJB 3.0 and JPA - Framework
• Flex Java Developers
• The @configuration annotation example in Spring 3.0 Framework
• Difference between JDBC 3.0 & JDBC 4.0
• Features of EJB 3.0
• Flex Developers
• What's new in JDBC 3.0?