i�ve been studying for assignment, thus i was thinking to create an structure using j2ee design patterns below and i�d like your comments:
Intercepting Filter -> Front Controller -> Business Delegate -> Session Facade -> Application Service -> BussinessObject -> DataAccessObject
and Service Locator, used for locate home.
Presentation Tier ------------------ Intercepting Filter - filter any request for security Front Controller - controlling request/response flow Business Delegate - encapsulating remote�s exception
Bussiness Tier ------------------ Session Facade - grouping many Application Service Application Service - could be used to group a use-case and business logic in general way, can use many business objects. Bussiness Object - contain specificaly bussines logic for each entity bean, where i create one BO for each entity when necessary.
Integration Tier ------------------ DAO - for retrieval list using Fast Lane Reader.
Did you think in the integration with the credit card payment ? and the frecuent flier system ? how to model this with your design, paterns to use, etc... ? And i not understand completly the objetiv of the buseniseObject ... no better to put the logic in the application service objetc ? what is the concrete objetives of echar object in the design ? in general terms i agree with your design ... i working in the second part two .. so discus this is very usefully for me ...
Santiago Urrizola : La Plata - Argentina<br />SCEA (89%-92%)<br /><a href="http://gpitech.wordpress.com/" target="_blank" rel="nofollow">http://gpitech.wordpress.com/</a>
posted 12 years ago
An integration with credit card payment and frequent flyer system i could use a application service, it could be called by other application service for payment and mileage if necessary.