• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EAO's

 
Aditya Vasudeva
Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am reading EJB3 in Action. Chapter 12 describes the concept of Entity Acces Objects(EAO). I read it but could'nt understand it very well. Could anyone please explain the concept with an example for proper understanding !!
 
J J Wright
Ranch Hand
Posts: 254
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
OK, I just had a very brief look at this. It appears, as the book suggests, to be a variation on the DAO pattern. They're suggesting that you should decouple you're entity access code from your session bean code (in case you want to use some other persistence technology). What you end up with is a manager class for an entity, which hides the data access code from your session bean. I'm not sure I see a whole lot of value in this myself. If you're using EJB 3.0 why wouldn't you want to use JPA?

If you don't understand the DAO pattern have a look at the Sun Blueprint pages - http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic