Hi All My question is in two parts 1) In my perspective the control object is same as the servlet controller in the MVC architecture, if thats the case any request/ response from/to the actor in a use case has to go from the boundary object and through the control ojbect Is my hypothesis wrong ??? 2) Those of you who have a passed / finished the class diagrams include the boundary / control objects in their class diagrams ?? Thanks for ur time guys Eric
Hi I have currently working on the assignment, and I do plan to include the Front Controler in my class diagram, but since I will be only using a single Front Control and handles all the requests from the client, I dont think it is going to take up too much of space. Just as there is a single Front Controller in the Web Tier that handles all the HTTPRequests from Web Clients, similarly there will be Front Controller in the Enterprise Application Tier ( Session Bean ) that handles all the busiiness requests from the Web Tier and the Java Application used by Travle Agents. In this desing the only job of the FrontController in the web tier is to take the HTTPRequest from the Web Client, translate this request into a business request that can be handled by the Front Controller in the EJB Tier. This is exactly the similar desing to Pet Store 1.0.1
Hi I am still analysing the sequence diagrams for each use case, so probably by the time I come to the class diagram as u r suggesting the control objects could merge. If u see my question 1, I was not clear but I was referring to the sequence diagrams. I am bit confused bcos in the book Enterprise Java with UML the author was directly accessing the life cycle objects from the User Interface.