Can you confirm that your presentation layer also include Controllers (Servlets), Service locators, Business Delegates and DTO's ?
For the TA's, you can represent the client tier with a desktop sorta system. You can rightly depict its controller and the Business Delegate in the presentation tier and everything else fits in place.Service Locators could be either Web-tier ServiceLocator or EJB tier ServiceLocator depending on the service and your caching requirements. DTO's will obviously be a part of the business tier
Originally posted by Senthil Rajendran:
Ray,
If you browse through the below "SUN" links you can find contradictory opinions. in the second link they advise to use the same controller for different types of client and in the first link they advise to have seperate controller. I just wanted all my objects to be cohesive, so I have used 2 different controllers.
Application client is not going to generate any events so I deceided not to use a web controller there.
http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/web-tier/web-tier5.html#1078111
http://java.sun.com/blueprints/guidelines/designing_enterprise_applications/client_tier/multiple_types/index.html#1028399
BTW Ray I have got a question Have you depcited "Ticket" in any of your models ? is'nt it a part of the domain model ?
Thanks,
Senthil
Originally posted by Senthil Rajendran:
Hi Dhiren,
Based on what I read as tips by SCEA passouts and other books
this is what I have done
1. Client-Tier package - Has two more packages
1.1 Web-UI package
1.2 Java-UI package
2. Web-Tier package
2.1 Web Package
Filter,front controller,Request Processor,HTML Actions,Events,Web Controller
2.2 Application Web Package
Filter,front controller, Business Delegate
2.3 Common
Service Locator (will be used by both the clients to hit application controller)
3. EJB-Tier package - has EJB Contoller, EJB Action and EJBs.
4. EIS-Tier package - has database and external systems.