Hi, i'm currently trying to complete part 2 but am having real problems with level of detail. When the assignments says that the solution must support both web client and java application client, how much detail do they need in the design of these clients. I find it hard to find any information on designing a swing client for j2ee, every resource talks almost exclusively about a web client. In the component diagram do we need to include all jsps? and what is the corresponding swing component button + button model etc? any help appreciated!
Hi Laura, be aware of the follwoing: You have to provide the architecture, no design details! how much detail do they need in the design of these clients. Client desing is not necessary, but provide diagrams for both web tier and ejb tier. In the component diagram do we need to include all jsps? Yes. JSP Pages are components of the web tier. and what is the corresponding swing component button + button model etc? Use MVC! Thomas
Joined: Feb 09, 2004
Hi Thomas , Fair point about the design, I'm a coder trying to do this certification so that would explain the problem wih detail. When you say use MVC I'm not really sure what you mean, there are documented ways of using model 2 in connection with JSP and i don't have a problem visualizing the solution there, but Swing/application client is another story. Swing by definition is loosely based on MVC so the different components have ususally a model e.g buttonmodel, and then the view/controller incorportated into the UI delegate. Does this mean then that i can have components called for example "ui delegate" and then another called <name>Action, one called <business delegate> etc? Also if you use the stereotype to describe the pattern, should you use the component name to describe what it is? jsp, servlet, java class etc?
Joined: Nov 23, 2002
With MVC I meant the model 2 architecture. To support both web and application clients there are several strategies 1. application client sends requests direcly (RMI-IIOP) to the ejb tier or 2. common controler (HTTP) for both client types in the web tier. 3. Use a protocol router Choose one and document your decision! Take a look in to the J2EE 1.3 blueprints chapter 3 Client Tier and chapter 126.96.36.199 Serving multiple client types. Use stereotypes for the J2EE components in your component diagram(s). Thomas