struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <Craig.McClana...@eng.sun.com>
Subject Re: Difference between Turbine and Struts
Date Fri, 23 Jun 2000 04:07:25 GMT
I am by no means an expert on Turbine's features, but the following
points highlight some of the differences and similarities.

* Both environments focus on the key goal of the MVC design
  pattern -- separation of business logic from presentation logic
  so that you can update either with minimal impacts on the
  other.

* Turbine is substantially more full-featured in it's approach,
  partly due to its much longer lifetime to date and partly by
  design (for example, it includes connection pools and lots
  of integration with other components).  Struts is very narrowly
  focused on the basic MVC controller function and a
  custom tag library.

* Turbine is somewhat agnostic about what technology you
  use for the presentation layer, although it is best integrated
  (from what I understand) with Webmacro.  Struts is focused
  on working with JSP as the presentation layer.

* Turbine's mechanisms often predate emerging Java standards
  for many types of resources, so it's no surprise that they aren't
  compatible.  Struts will, to the extent it adds any features later,
  be extended in ways that are compliant with the emerging J2EE
  family of API standards.

Turbine is an excellent framework that doesn't really have much synergy
with JSP pages at the moment -- although there is talk of extending in
that direction.  Struts is a new framework (quite good IMHO :-) that is
focused on the synergies that JSP custom tags offer to reduce the
workload of creating web applications, coupled with an implementation of
a good design pattern (same as Turbine's) for the overall application.

Craig McClanahan




Mime
View raw message