Instead of accessing the ENINTY Bean directly, Â You access the client through Session bean, i.e you call session bean first which in turn calls entity bean, this is called session facade
A SessionFacade acts like a wrapper class which exposes necessary methods of all the beans present in this class , these beans might be entity or session . On calling the method of this class we should write code to call the method on the respective bean i.,e we need to write code that redirects the call to the respective bean which was supposed to handle the request. This class should typpically need to be a remote bean and this shoul act as pont of entry to all other local beans . By this we reduce the network traffic as only once object proxy is being travelled from server to the client.
Session facade is one design pattern that is often used while developing enterprise applications.
It is implemented as a higher level component (i.e.: Session EJB), and it contains all the iteractions between low level components (i.e.: Entity EJB). It then provides a single interface for the functionality of an application or part of it, and it decouples lower level components simplifying the design.
Basically we wrap all the calls inside a Session Bean, so the clients will have a single point to access (that is the session bean) that will take care of handling all the rest.
