《《5.2 J2EE Design Pattern》.ppt

5.2 J2EE Design Pattern 1. Consider an online banking scenario where a servlet receives a request to transfer funds from one account to another, Summary three questions: 1.Reduce network overhead2. Avoid large transaction 3. Separate business logic What problems? Session Fa?ade Pattern Solution : Wrap the entity bean in a layer of session beans called the Session Fa?ade. Clients should have access only to session beans not to entity beans 5.2 J2EE Design Pattern 1. Consider a simple Web-based airline registration system in which a servlet receives a request to reserve a seat for a user for a flight Solutions?? Requirements Acceptable response time Reliable Message Facade Use message-driven beans to create a reliable( fault-tolerant), asynchronous fa?ade. Clients should have access to message-driven beans only, not to entity beans 5.2 J2EE Design Pattern EJB Command : Wrap business logic in lightweight command beans that decouple the client from EJB, execute in one network call, and act as a fa?ade for the EJB layer. Improve extensibility 5.2 Other J2EE Design Patterns Business Delegate Pattern Service Locator pattern DTO Pattern Front Controller pattern Incepting Filter Pattern * UserHome Servlet User Account Home Account1 Account2 findByPrimary(pk) findByPrimary(account1pk) findByPrimary(account2pk) authorized() withdraw(amount) deposit(amount) F A C A D E F A C A D E client1 client3 client2 UserHome Servlet AirlineHome Airline Flight findByPrimary(pk) registerAirline(aUser) getFlight(FlightNum) findByPrimary(airlinepk) areSeatsAvailable() reserveSeatFor(aUser) *