tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Tapestry Wiki] Update of "FrameworkComparisons" by DanielJue
Date Wed, 19 Mar 2008 16:25:27 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.

The following page has been changed by DanielJue:

  == When to use Tapestry ==
   * If you have a one or more designers (the artsy-people) who like to modify HTML documents
instead of things like JSPs.
   * If you don't like dealing with XML configuration (Tapestry 5)
  == When not to use Tapestry ==
   * If you are stuck on Java 1.4 or are otherwise forbidden from using annotations and Java
1.5 features.
@@ -21, +20 @@

  Some of these are addressed elsewhere in the Tapestry documentation.
   * Static Structure, Dynamic Behavior.  This is not as limiting as it may seem, and the
benefits are worth it.  Usually this issue comes up when users want hot-pluggable components,
like what you can get using a PHP based Content Management System.  In almost all cases, the
user just needs to apply some creative thinking in order to accomplish the goal, while still
using a static structure.  It may also require you to redefine your notion of "structure"
and "behavior" depending on which frameworks you have used previously.
+  * Using Maven.  For many users, Tapestry 5 may introduce you to Maven for the first time.
Many T5 tutorials use Maven to get you started (archetypes, screencasts, articles, appfuse),
but you are not required to use Maven at all.  To restate, Maven has never been a requirement,
only a convenient way to deal with dependencies and builds.  So it may be a development burden
to stay up to date if your particular build tool doesn't find that dependency of a dependency
of a dependency for you.
  = Comparisons to previous versions of Tapestry =
  This is addressed elsewhere, and it was done so early on because it is a hot topic.  Tapestry
tends to make use of new technology as the years pass, and many times that has resulted in
major change.  Granted, this usually happened on Major revision changes, so some incompatibility
is to be expected as with any framework.  Tapestry 5 (T5) was designed so that any future
changes would have less of an impact.
  = Quick Comparisons to Other Frameworks =

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message