struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sandeep Takhar <>
Subject Re: Struts MVC framework similar to that of a servlet container?
Date Mon, 21 Jul 2003 12:38:21 GMT
there's a lot of stuff it gives you out of the box.

1. solid code
2. validation framework
3. tile framework
4. auto-population framework
5. role based actions
6. xml configuration of all the links or actions of
your application
7. best practices framework bundling (scaffolding)
complete with examples (many years of experience went
into this one).
8. ease of use

I am missing about twice as many things from this list
I am sure...

the servlet container is sun's way of making sure that
what you build is timeless (and works on their

Struts solves common problems across every typical
application.  The servlet container does not solve
these typical problems.  Struts is really a pattern...

--- Ranko Bijelonic <> wrote:
> Hi.  I've been using Struts for a long time, and
> I've been very happy with
> the framework.  However, a recent discussion on
> Sun's Java forums has left
> me wondering if Struts is necessary.  It seems that
> the servlet container
> itself provides an MVC framework very similar to
> that of Struts.  All that
> is missing is some utilities and standardization.  I
> was wondering if there
> is a flaw in my logic below, and if anyone had any
> comments.
> In comparing these two MVC frameworks, the servlet
> container would be the
> equivalent of the ActionServlet.  They both read
> their configuration files,
> examine the incoming URL, and then forward the
> request to the configured
> handler.  In the case of the servlet container the
> handlers are Servlet
> classes, and in the case of Struts its the Action
> classes.  Both the
> container and the ActionServlet will create an
> instance of their handler
> when its requested the first time. The Servlet's
> service method and the
> Action's execute method will call some domain logic
> and then select a view
> to display to the user.  The Servlet can use
> RequestDispatchers to
> encapsulate information about the view, and the
> Action will use an
> ActionForward.  Doesn't this sound very similar?
> It seems like we are adding a lot of complexity on
> top of the servlet spec
> in order to get some common tasks done for us.  But
> that could probably be
> better done by the servlet container itself.  For
> example, Struts
> automatically populates the form class the developer
> specifies for a
> particular Action.  But Sun could provide a standard
> Filter implementation
> which does the same thing.  You can declare handlers
> for your exceptions in
> the Struts configuration file, but you can also do
> it in the web.xml.  If
> the functionality there is not quite the same, Sun
> can add a little to the
> spec and we would get it.
> My question is, is an application built in Struts
> really that much more
> maintainable than one built with servlets?  Or if
> some common utilities
> provided by the Struts container were provided by
> the servlet container,
> would there be much difference?  It seems that would
> even be simpler.  Or
> not?
> ranko
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message