This is called the Sesion Facde pattern. It's premise is to ease network traffic, protect server-side resources and other aspects of y9our system. See Core J2EE Patterns for a discussion of this pattern.
Ken Litwak > >Hi gurus, > >I've tried many EJB sample codes, and got a question. >I've seen many samples that client(java applicaton, servlet or JSP) >calls Session Beans which call Entity Bean. >Why ? > >Why many codes do like below ? >client --> session bean --> entity bean. >Why NOT like below ? >client --> entity bean. > >I guess that client calls entity bean directly is faster. > >hm...Are there any advantages of doing "client --> session bean --> >entity bean" ? > >or just For keeping a session between client and ejb ?? > >Thanks in advance > >=========================================================================== >To unsubscribe, send email to [EMAIL PROTECTED] and include in the body >of the message "signoff EJB-INTEREST". For general help, send email to >[EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
