• Post Reply Bookmark Topic Watch Topic
  • New Topic

J2EE Patterns

 
pradeeppk
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In an application that follows the MVC Architecture, we want to implement the Business Delegate and Session Facade patterns.
The flow we have decided is as follows:
Any request from the JSP is routed to the Controller Servlet. The Servlet will talk to a Business Delegate, which in turn will delegate the call to a Session Facade. The Session Facade decides (it contains the Session Bean lookup logic plus the Business Logic) which Session Bean to talk to. The Session bean in turn will lookup the Entity bean that will talk to the Database.
The outbound response will follow the revesre path.
DO YOU THINK THIS WILL BE AN EFFICIENT DESIGN? PL ADVISE.
 
Marcos Maia
Ranch Hand
Posts: 977
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by pradeeppk:

DO YOU THINK THIS WILL BE AN EFFICIENT DESIGN? PL ADVISE.

yes, but you should also consider implementing a command pattern to help handling the client requests with the Front Controller Servlet, another thing is implementing a Service Locator wich could cache remote home references/home handles to your Session Facade what can improve the performance of your application significativelly.
regards.
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why do you need the second layer of Session beans? The Session Facade usually talks directly to either BO's/DAO's or (in simple cases) Entity beans. You are simply adding unneeded overhead with the second layer of Session beans.
Kyle
 
Kishore Dandu
Ranch Hand
Posts: 1934
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Pradeep,
You need to login according to the naming conventions of this site.
Please be aware.
Kishore.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!