Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JSF EJB3 JPA , what are the design patterns. Most of design patterns of J2EE doesnt make sense..

 
brijesh chavda
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

This is a general design level question.

1.) I am using EJB3+JPA and JSF for presentation. What is the best pattern to use backend objects in presentation layer.
I am planning to use Stateless session bean as a facade to entities and use detached entities from managed bean. Is this acceptable approach? . Is there any value addition for using DAO or DTO pattern here.

2.) Should i put detached entities in HttpSession or i should create statefull session bean and put its handle to http session?

3.) Does it make sense to maintain cache of entities at presentation layer for performance for e.g Product catalogue.

4.) What is the naming convention for the managed bean , should it be called Controller? For e.g UserController or Managed Bean, like UserManagedBean.

Thanks for helping me out.

Brijesh
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35279
384
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1) Yes, that makes sense. YOu are correct that most of the old design patterns aren't needed.
2) Depends on your requirements. You'll need to decide this as architect
3) Depends on your requirements. You'll need to decide this as architect
4) see here

I'm deliberately not answering these questions because part 2 is an individual assignment.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic