Struts Tutorials:
Struts2 Tag CheckBoxList
, Checkbox, Iterator, IF
Struts2 Tag Library Example
Struts2 Tiles Example
Struts2 Tiles I18N Example
Struts2 Questions
Struts Tiles I18N Example
Struts Eclipse MVC
Struts2 Tags
Struts2 Example and Tutorial
Struts MVC
Struts2 Validation
Hibernate Tutorials:
Hibernate Case Study
Class Hierarchy Persist Example
Using Hibernate Interceptor
Hibernate Questions with Answer
Hibernate Many-to-Many Mapping Example
Hibernate one-to-many Mapping Example
Hibernate and ORM tools
Spring Hibernate Example
Hibernate SessionFactory Example
Hibernate Mapping Class Hierarchy
Hibernate Questions
Hibernate SessionFactory Questions
Spring Hibernate Example:
Spring Hibernate Case Study
Written By : ISHTEK
Title :
Session Facade
Description :
Advantages Discussed
More...
|
Written By : ISHTEK
Title :
DAO Data Access Object
Description :
Advantages Discussed
More...
|
Written By : ISHTEK
Title :
Business Delegate
Description :
Advantages or Benefits discussed
More...
|
| Advantages-Discussed - Session-Facade - J2EE-Design-Patterns Example
Author : ISHTEK
Date (Year/Month/Date): 2009-05-26
Advantages or Benefits of Session Facade J2EE Design Pattern
What are the benefits or advantages of Session Facade J2EE
Design Pattern ?
To my understanding, Session Facade is the entry point/ access point
to business services, those are deployed in form of transactional,
secure, clusterable, distributed business code/bean in EJB Container.
I think,
1. Session Facade Design Pattern can facilitate in achiving
coarse grain method calls, to reduce number of fine-grain remote
method calls to minimum.
As each remote method call is RMI communication from stub to skeleton
with marshal and unmarshaling of objects passed as method argument/
parameter by value. Method call is delegated to the EJB Container
and EJB Container manages life cycle of Enterprise JavaBean, and
invokes method on the deployed component.
2. Session Facade Design Pattern can help in managing
transaction and security services, by reducing potential number of
entry points or methods to the business services.
3. Session Facade Design Pattern can use declarative
transaction and security services, by configuration of session bean,
thus complexities related to transactions and security services are
substantially reduced, in comparison to programmative transaction
services like JTA.
4. Session Facade Design Pattern can facilitate scalling of
businees side code of application to suit availability and failover
and load balancing criterials/Non Functional Requirements(NFR).
5. With Session Facade Design Pattern, caller can be any program
that has JNDI implementation, on Java Platform.
6. If Session Facade Design Pattern is made stateless, then
caller can be served by any node in the cluster and thus no need for
session replication overheads across different nodes in cluster
environment.
These are my own understanding only, If you are interested in adding or
contracting any of these, you are most welcome to do so just by writing or
commenting on this Page.
| |
<- requires login
