• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

JPA vs Entity Bean

 
Ranch Hand
Posts: 3852
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

It looks very weird question but please share your thoughts.

What are the advantages and disadvantages of using JPA over Entity Bean?

My points are:

Advantages:

1.JPA uses POJO classes, that makes it lighter.
2.POJO classes can implement Serializable interface, so no need for DTO.
3.No need for EJB container (or Application Server).

Disadvantage:
1.Being a new technology, time required for developers to understand and code.

Please put more points.

Thanks.
[ October 09, 2007: Message edited by: ankur rathi ]
 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JPA allows you to have a really OO models using inheritance and polymorphism.

JPA allows you to choice the implementation you will use (this one provided by the AS, Hibernate, Toplink,...)

JPA can be used directly in the web tier... Its is possible to use JPA without EJB...
 
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
POJOs can be tested easily, since they do not require a special environment like an EJB Container.
 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Easy configuration via metadata support
 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JPA is usable not only for JavaEE but also for JavaSE.
 
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JPA is used for persistence to relational databases, whereas Entity Beans (BMP) can persist on to any datasource (legacy systems, OODB, non-relational datasources etc).

JDO specification also allows for storage to RDBMS, OODBMS, files, XML etc.
[ October 14, 2007: Message edited by: chris zielinski ]
 
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think JPA allows us to model coarse-grained objects - by using OO design relationships - such as inheritance, etc. Entity bean, due to their nature probably, in my opinion, suited towards fine-grained objects.
 
He loves you so much! And I'm baking the cake! I'm going to put this tiny ad in the cake:
Garden Master Course kickstarter
https://coderanch.com/t/754577/Garden-Master-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic