Charles,
In my understanding, Struts fulfills the Controller part of MVC architecture. Please find the related technologies that are considered View components in struts world. Also find the related technologies that are considered Model components in struts world. The information is attached at the end of the e-mail.
Another distinction I see is, EJB is a model(Entity Beans)/controller(Session Beans) component. EJB components do not care for which presentation layer is used. But Struts is geared towards presentation layer in web technologies world.
I agree to the fact that EJB does not have to be the model component architecture for an application. The non-functional requirements dictate whether the application's model component (if you choose to use STRUTS) is a complex, yet robust EJB components or simple, not so robust JDBC components.
Hope this helps!!
Thanks and Regards,
Sree/-
Struts provides its own Controller component and integrates with other technologies to provide the Model and the View. For the Model, Struts can interact with any standard data access technology, including Enterprise Java Beans, JDBC, and Object Relational Bridge. For the View, Struts works well with JavaServer Pages, including JSTL and JSF, as well as Velocity Templates, XSLT, and other presentation systems.
Struts provides the control layer for a web application. Developers can use this layer with other standard technologies to provide the data access and presentation layers. Some popular Data access technologies include:
Presentation layer technologies include:
Other data access and presentation systems are listed in the Struts Resource Guide.
I'd like to foment a little discussion regarding what I consider a key
choice in architecture for a J2EE based system. I have not found
specific literature that addresses this.
Given that you can choose to use Struts or EJB or some combination of
the two, what factors drive your decision? What are the advantages of
using EJB at all when Struts can probably get the job done? My feeling
on this is that a lot of architects are pounding away on EJB
implementations that are generally more expensive and complex to develop
and maintain than a good JSP MVC framework. A clear delineation of when
and why EJBs need be used over Struts would be real helpful to budding
architects here.
Thanks.
Charlie