Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Stateless DAO(EAO) versus POJO DAO

 
Luciano A. Pozzo
Ranch Hand
Posts: 112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is it better to use DAO as stateless or DAOs as POJO? What are the advantages and disadvantages?

thanks
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34196
340
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Luciano,
It depends on what is in your DAO. Personally, I find it easier to write them as POJOs because I store state for the duration of the query. If your DAO is just a facade to something else (like a JPA entity), stateless is fine.
 
Luciano A. Pozzo
Ranch Hand
Posts: 112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Jeanne,

Actually I do not store state, only delegate queries for the EntityManager. Here's an example of DAO that I am currently using:




But there came the idea of not using stateless, as example below:



The argument about this second way(just a POJO) is to improve performance.

Makes sense?
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34196
340
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Luciano A. Pozzo:
The argument about this second way(just a POJO) is to improve performance.

Makes sense?

Kind of. It sounds like a case of premature optimization to me. If you have a problem with performance on that segment, sure. But I would think the database code would take many times longer than creating/injecting an object.
 
Luciano A. Pozzo
Ranch Hand
Posts: 112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thank you for your opinion Jeanne.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic