There is a general principle of a "single point of access" for MVC 2 web applications, that is, each request is processed by single Controller servlet which analyzes the request contents, invokes request-specific server-side Actions (e.g. interacts with EJBs), updates server-side JavaBeans objects Model and forwards the control to the JSP page representing View , which in turn acceses server side objects (JavaBeans) and generates client View of the server-side Model data. How does this fit in WAE? Is it possible to model such an architecture and behavior with WAE? What are general principles for modelling MVC2 architecture with WAE (Consider, that there are 1:1 ServerPage-ClientPage mappings, but each link on ClientPage is directed to the common, single Servlet, which in turn redirects it to the apropriate ServerPage)? Should I create any new stereotypes (servlet, action)?

See also: Struts framework at http://jakarta.apache.org