You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by hu...@apache.org on 2006/02/19 16:30:40 UTC

svn commit: r378911 - in /struts/site/trunk/xdocs: index.xml kickstart.fml

Author: husted
Date: Sun Feb 19 07:30:40 2006
New Revision: 378911

URL: http://svn.apache.org/viewcvs?rev=378911&view=rev
Log:
Kickstart FAQ 
* Add entries about choosing a technology for new development 

Modified:
    struts/site/trunk/xdocs/index.xml
    struts/site/trunk/xdocs/kickstart.fml

Modified: struts/site/trunk/xdocs/index.xml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/index.xml?rev=378911&r1=378910&r2=378911&view=diff
==============================================================================
--- struts/site/trunk/xdocs/index.xml (original)
+++ struts/site/trunk/xdocs/index.xml Sun Feb 19 07:30:40 2006
@@ -76,34 +76,36 @@
                     ,
                     our development community chose to "make new friends but
                     keep the old".
-                    Some of us want (or need) to stick with the original
-                    request-based framework.
-                    Others are ready to switch to an component-based framework
+                    Some of us want to stick with a request-based framework.
+                    Others are ready to switch to a component-based framework
                     that builds on JavaServer Faces.
                     We offer both frameworks because we have volunteers to
                     create and maintain both frameworks.
                 </p>
 
                 <p>
-                    If you are starting a new project, you might want to
-                    consider our Shale
-                    Framework. Some people feel that JSF and Shale is the
-                    quickest way to
-                    write new Java web applications. Others, however, prefer
-                    the URL
-                    mapping style of a request framework. No matter what your
-                    preference
-                    is, we offer an actively developed framework for you. If
-                    you are not
-                    sure which to use, go ahead and try them both out.
-                </p>
-
-                <p>
                     If you have mature Action Framework applications in
                     production, don't worry,
                     we are still here, same as ever.
                     After all, we have our share of mature application in
                     production too.
+                </p>
+
+                <p>
+                    If you are starting a new project using new technology,
+                    don't worry, we are still blazing trails, same as ever.
+                    For new JavaServer Faces project, we offer the Shale
+                    Framework.
+                    For new JSP projects, we offer the original Action framework.
+                    Soon, we will also offer a new Action 2 framework, based on
+                    <a href="announce.html#a20051214.3">WebWork</a>
+                    technology.
+                </p>
+
+                <p>
+                    Whether you are staying the course, or ready to leap forward,
+                    the Apache Struts project is here to help you do what you want
+                    to do.
                 </p>
 
                 <p>

Modified: struts/site/trunk/xdocs/kickstart.fml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/kickstart.fml?rev=378911&r1=378910&r2=378911&view=diff
==============================================================================
--- struts/site/trunk/xdocs/kickstart.fml (original)
+++ struts/site/trunk/xdocs/kickstart.fml Sun Feb 19 07:30:40 2006
@@ -241,6 +241,11 @@
                     Ti has become a proposal to put the WebWork wheel back on
                     the Struts axle.
                 </p>
+                <p>
+                    At this point, the Ti codename is being dropped,
+                    and we are referring to the incoming WebWork codebase as Action
+                    2.
+                </p>
             </answer>
         </faq>
 
@@ -279,24 +284,6 @@
             </answer>
         </faq>
 
-        <faq id="ti2">
-            <question>Does Ti mean there will be three frameworks?</question>
-            <answer name="Does Ti mean there will be three frameworks?">
-                <p>
-                    There will be the
-                    <strong>Action 1</strong>
-                    framework that is currently
-                    in production and usually refered to as "Struts".
-                    When released, Ti will become the
-                    <strong>></strong>
-                    Action 2 framework.
-                    Shale will remain a separate but equal framework
-                    that focuses on JavaServer Faces rather than
-                    conventional server pages.
-                </p>
-            </answer>
-        </faq>
-
         <faq id="overdrive">
             <question>What about OverDrive or Struts Nexus?</question>
             <answer>
@@ -325,6 +312,175 @@
             </answer>
         </faq>
 
+        <faq id="choice">
+            <question>Which Apache Struts Framework should I use on my next
+                project?</question>
+
+            <answer>
+                <p>
+                    First, you should decide which user interface technology you
+                    would like to use:
+                    <a href="http://java.sun.com/j2ee/javaserverfaces/">JavaServer
+                        Faces</a>
+                    (JSF),
+                    conventional
+                    <a href="http://java.sun.com/products/jsp/">JavaServer Pages</a>
+                    (JSP),
+                    or another templating technology like
+                    <a href="http://jakarta.apache.org/velocity/">Velocity</a>
+                    .
+                </p>
+                <p>
+                    JSF is designed to work well with visual design tools, much
+                    like ASP.NET.
+                    A good place to learn more about JSF is
+                    <a href="http://jsfcentral.com/">JSF Central</a>
+                    .
+                </p>
+                <p>
+                    Conventional JSP is a tried and true strategy.
+                    When used as part of a MVC architecture, applications based on
+                    server pages are easy to create, maintain, and extend over time.
+                </p>
+                <p>
+                    If you are a sole developer working on a small application,
+                    then you might not even need a framework.
+                    Simple applications can be written with JSF or JSP with
+                    <a href="http://java.sun.com/products/jsp/jstl/index.jsp">
+                        JSTL</a>
+                    "out of the box."
+                    If you choose JSF, be sure to give
+                    <a href="http://developers.sun.com/prodtech/javatools/jscreator/">
+                        Java Studio Creator</a>
+                    a try.
+                </p>
+                <p>
+                    Multi-developer teams working on larger applications will
+                    probably find a MVC framework useful. In that case,
+                    we would suggest
+                    <a href="http://struts.apache.org/struts-shale/index.html">Struts
+                        Shale</a>
+                    for JSF
+                    or
+                    <a href="http://struts.apache.org/struts-action/index.html">
+                        Struts Action</a>
+                    for JSP
+                    .
+                </p>
+            </answer>
+        </faq>
+
+        <faq>
+            <question>So many decisions! Shouldn't it be simplier?</question>
+            <answer>
+                <p>
+                    Yes, there seems to be nothing but choice when it comes to
+                    developing web applications.
+                </p>
+
+                <p>
+                    To begin with, someone has to choose between ASPX, Java, PHP,
+                    Python, Ruby, et al.
+                    Once you choose Java, then you have to choose a web container,
+                    such as Jetty, Tomcat, Resin, WebLogic, or WebSphere, to name a
+                    few.
+                    Of course, you also have to build the application that runs in
+                    the container, which is where
+                    <a href="#choice">choosing Apache Struts</a>
+                    comes in. Then, most teams also use a data access framework.
+                    Choices there include Cayenne, iBATIS, Hibernate, and OJB.
+                </p>
+
+                <p>
+                    (Right about now, Ruby's single-stack approach must be sounding
+                    pretty good!)
+                </p>
+
+                <p>
+                    But, wait, there's more! You also have to choose an editor or
+                    IDE:
+                    Eclipse? IDEA? NetBeans? UltraEdit? Some other?
+                    (Many teams decide to use more than one!)
+                    And do we use Ant, Maven, or the IDE to build it all?
+                </p>
+
+                <p>
+                    Lest we forget: Someone also needs to choose a database system
+                    (DB2? Derby? Oracle? MySQL?), a version control system (CVS?
+                    Subversion? Perforce?),
+                    a development methodology (eXtreme Programming? RUP? Scrum?
+                    Waterfall?),
+                    and, if you're lucky, an issue tracker (Bugzilla? JIRA? Scarab?).
+                </p>
+                <p>
+                    Welcome to the jungle!
+                </p>
+            </answer>
+        </faq>
+
+        <faq id="next">
+            <question>
+                Is Shale the Next Struts? Or is Action 2 the Next Struts?
+            </question>
+            <answer>
+                <p>
+                    Yes.
+                </p>
+                <p>
+                    Shale is the Next Struts for JSF. Action 2 is the next Struts for
+                    JSP.
+                </p>
+                <p>
+                    If you'd like a head-start on Action 2,
+                    you could start new development with WebWork 2 today.
+                    <a href="announce.html#a20051214.3">
+                        WebWork is joining Apache Struts</a>
+                    ,
+                    and Action 2 will be an updated release of WebWork 2.2.
+                    Undoubtedly, there will be some changes,
+                    but the core API and architecture will remain the same.
+                </p>
+            </answer>
+        </faq>
+
+        <faq id="steering">
+            <question>Shouldn't the Apache Struts team focus on a single technology
+                and help reduce choice for the rest of us?</question>
+            <answer>
+                <p>
+                    Apache Struts is neither a steering committer nor a vendor. We're
+                    a group of engineers creating the web application frameworks that
+                    we want to use to build our own applications. Some of us are
+                    working on JSF applications, some of us are working on JSP
+                    applications, and some of us are working on both. Since we have
+                    volunteers to work on two frameworks, we offer two
+                    frameworks.</p>
+
+                <p>The Struts committers all work for different employers all over
+                    the world, and it's not possible for us to say this technology or
+                    that technology is the only one anyone in our group can use.
+                    One of our employers might choose JSF, and another might stick
+                    with JSP. We are a working group of engineers who live in the
+                    real world, and we are faced with all the same choices every Java
+                    engineer faces today.
+                </p>
+                <p>
+                    Entities like Microsoft, and Sun, and Zend, exist to promote one
+                    technology over another, mainly to make it easier for them to
+                    sell you something.
+                    The Apache Struts team is not trying to sell you anything.
+                    We're collaborating on the frameworks that we want to use, and
+                    we are trying to share the wealth with others who might want to
+                    help us.
+                    If you choose to use one of our frameworks, that's great. We're
+                    glad we could help. If you'd like to help us make the frameworks
+                    even better, feel free to return the favor. We don't want your
+                    money, but
+                    <a href="helping.html">we could use your help</a>
+                    .
+                </p>
+            </answer>
+        </faq>
     </part>
 
     <part>



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