Hi all, for example, I have a ASP page that query data from a StoredProcedure and shows in a HTML table... now I want to substitute the ASP for a JSP and the StoredProcedure for a EJB... when I must use the patern Composite Entity or the Session Facade? Or better, to substitute the StoredProcedures for EJBs, which they could be a Composite Entity and which could be a Session Facade? They forgive me but these two patterns me had seemed similar.
Arent there any need for handling some transactions ? Is it always read and display ? In case there are transactions to be handled,go with Session facade.Also,Use SessionFacade Pattern to avoid direct client access to Entity beans thus reducing network calls... If the system just retrieves and displays then you can just go with Composite Entity beans. Just keep this in mind when you design - The Composite Entity Pattern improves performance significantly by reducing number of entity beans in an application provided the relationships between the tables have been designed well to support the same. Folks,please correct me in case i am wrong .. :roll: [ January 31, 2005: Message edited by: Maybach Smith ]
You don't like waffles? Well, do you like this tiny ad?