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/11 14:23:31 UTC

svn commit: r376979 - in /struts: action/trunk/xdocs/faqs/kickstart.fml site/trunk/xdocs/kickstart.fml

Author: husted
Date: Sat Feb 11 05:23:30 2006
New Revision: 376979

URL: http://svn.apache.org/viewcvs?rev=376979&view=rev
Log:
Documentation
* Update the merger FAQs

Modified:
    struts/action/trunk/xdocs/faqs/kickstart.fml
    struts/site/trunk/xdocs/kickstart.fml

Modified: struts/action/trunk/xdocs/faqs/kickstart.fml
URL: http://svn.apache.org/viewcvs/struts/action/trunk/xdocs/faqs/kickstart.fml?rev=376979&r1=376978&r2=376979&view=diff
==============================================================================
--- struts/action/trunk/xdocs/faqs/kickstart.fml (original)
+++ struts/action/trunk/xdocs/faqs/kickstart.fml Sat Feb 11 05:23:30 2006
@@ -82,7 +82,7 @@
                     implementation for a servlet 2.3 and JSP 1.2 container.
                 </p>
                 <p>After serving as the co-lead of the JSR 127 specification
-                    (JavaServerFaces), Craig created another version of Struts
+                    (JavaServerFaces), Craig created another rendition of Struts
                     based on JavaServerFaces, called Shale. Both Struts Action
                     Framework and Struts Shale are first-class citizens of the
                     Apache Struts project.</p>

Modified: struts/site/trunk/xdocs/kickstart.fml
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/kickstart.fml?rev=376979&r1=376978&r2=376979&view=diff
==============================================================================
--- struts/site/trunk/xdocs/kickstart.fml (original)
+++ struts/site/trunk/xdocs/kickstart.fml Sat Feb 11 05:23:30 2006
@@ -17,8 +17,16 @@
 // ======================================================================== 78
 -->
 <faqs title="Kickstart FAQ">
+
     <part>
+        <p>
+            Here are answers to the some of the usual Apache Struts
+            getting-started questions.
+        </p>
+    </part>
 
+    <part>
+        <title>Product Line</title>
         <faq id="shale">
             <question>Why are you offering both Struts Shale and Struts Action
                 Framework? Don't they compete for new development?</question>
@@ -56,15 +64,13 @@
             <question>Is Struts Shale a fork?</question>
             <answer>
                 <p>No. It's an entirely new product with its own architecture.
-                    Struts Shale is an MVC framework for web applications,
-                    like Struts Action Framework, but it's a fresh start.
-                    Struts Shale is the best choice for developers eager to
-                    leverage the latest technologies, like JavaServer
-                    Faces.</p>
+                    Shale is to JavaServer Faces what Action is to JavaServer
+                    Pages.
+                </p>
                 <p>Both frameworks will have a home here so long as there are
                     volunteers ready to contribute.</p>
                 <p>We encourage you to choose the framework that works best
-                    for you. (Even if it is not one of ours!)</p>
+                    for you.</p>
             </answer>
         </faq>
 
@@ -103,67 +109,83 @@
             </answer>
         </faq>
 
-        <faq id="2x">
-            <question>Is Shale likely to become Struts 2.x?</question>
-            <answer>
-                <p>
-                    Struts Shale has its own identity and its own release
-                    cycle.
-                    Struts Action Framework is one subproject, and the Struts
-                    Shale framework is another.
-                    So, no, it is not likely that Struts Shale will become
-                    Struts Action 2.x.
-                </p>
-            </answer>
-        </faq>
-
         <faq id="ti">
-            <question>What about Ti? What about WebWork?</question>
+        <question>What about Ti? What about WebWork?</question>
+        <answer>
+        <p>
+            <a href="http://wiki.apache.org/struts/StrutsTi">Struts
+                Ti</a>
+            (short for Titanium) is a codename for Struts Action
+            Framework 2.x.
+            In late November 2005, the Ti proposal was amended to
+            include a merger with
+            <a href="http://www.opensymphony.com/webwork/">Open
+                Symphony WebWork</a>
+            .
+            Under this plan, the next stable release of WebWork is
+            being donated to Apache Struts,
+            and the lead WebWork committers are joining the Struts
+            community.
+            The WebWork codebase is being brought into the ASF through
+            the Apache Incubator.
+            Once licensing and related issues are resolved,
+            the codebase will be made part of the Apache Struts
+            framework.
+        </p>
+        <p>
+            WebWork started as a
+            <a href="http://incubator.apache.org/learn/rules-for-revolutionaries.html">
+                Struts Revolution</a>
+            .
+            Over the years, it has evolved into a superb action-based
+            framework that retains many Struts 1.x paradigms.
+        </p>
+        <p>
+            People who have worked with both Struts 1.x and WebWork
+            2.x tend to agree that it is a logical candidate for
+            Struts Action Framework 2.x.
+            If you look the Struts Action 1.x roadmap and the WebWork
+            2.x feature set,
+            you'll see that WebWork has already does most of what we
+            wanted Struts Action to do.
+            If we finished the roadmap ourselves, Struts Action would
+            end up as a WebWork workalike.
+            Rather than reinvent the wheel,
+            Ti has become a proposal to put the WebWork wheel back on
+            the Struts axle.
+        </p>
+        </answer>
+        </faq>
+
+        <faq id="xwork">
+            <question>What about other Open Symphony products, like
+                XWork?</question>
+            <answer>
+
+                <p>
+                    For the time being, there is no plan to migrate XWork to
+                    the ASF. Struts Action has always had many dependencies on external
+                    packages.So long as packages like XWork and Sitemesh are doing well
+                    at OpenSymphony, there is no reason to make further changes.
+                </p>
+            </answer>
+        </faq>
+
+        <faq id="migrate">
+            <question>Will it be difficult to migration from Action 1 to
+                Action 2?</question>
             <answer>
                 <p>
-                    <a href="http://wiki.apache.org/struts/StrutsTi">Struts
-                        Ti</a>
-                    (short for Titanium) is a proposal for a Struts Action
-                    Framework 2.x candidate.
-                    In late November 2005, the Ti proposal was amended to
-                    include a merger with
-                    <a href="http://www.opensymphony.com/webwork/">Open
-                        Symphony WebWork</a>
-                    .
-                    Under this plan, the next stable release of WebWork would
-                    be donated to Apache Struts,
-                    and the lead WebWork committers would join the Struts
-                    community.
-                </p>
-                <p>
-                    WebWork started as a
-                    <a href="http://incubator.apache.org/learn/rules-for-revolutionaries.html">
-                        Struts Revolution</a>
-                    .
-                    Over the years, it has evolved into a superb action-based
-                    framework that retains many Struts 1.x paradigms.
-                </p>
-                <p>
-                    People who have worked with both Struts 1.x and WebWork
-                    2.x tend to agree that it is a logical candidate for
-                    Struts Action Framework 2.x.
-                    If you look the Struts Action 1.x roadmap and the WebWork
-                    2.x feature set,
-                    you'll see that WebWork has already does most of what we
-                    wanted Struts Action to do.
-                    If we finished the roadmap ourselves, Struts Action would
-                    end up as a WebWork workalike.
-                    Rather than reinvent the wheel,
-                    Ti has become a proposal to put the WebWork wheel back on
-                    the Struts axle.
-                </p>
-                <p>
-                    Of course, many of us have significant Struts Action 1.x
+                    Many of us have significant Struts Action 1.x
                     applications in production.
                     Being able to migrate both applications and developer
-                    skill sets is a telling point of the proposal.
-                    Both a migration layer and migration documentation are
-                    under active development.
+                    skill sets is important to all of us.
+                </p>
+                <p>
+                    Several
+                    <a href="http://wiki.apache.org/struts/MigrationStrategy">
+                        migration strategies</a>
+                    are being developed.
                 </p>
             </answer>
         </faq>
@@ -172,13 +194,16 @@
             <question>Does Ti mean there will be three frameworks?</question>
             <answer name="Does Ti mean there will be three frameworks?">
                 <p>
-                    Probably not.
-                    Like many projects, we start by giving proposed
-                    subprojects a codename.
-                    Sun's "Tiger" and Microsoft's "Vista" are two examples.
-                    "Ti" is a codename like "Tiger" and "Vista.
-                    If Struts Ti is accepted as Struts Action Framework 2.x,
-                    the codename would fall into disuse.
+                    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>
@@ -220,15 +245,12 @@
                     discrete subprojects. Struts Classic is a codename for the
                     work we needed to do to create and release the new
                     subprojects.</p>
-                <p>For a time, we considered bundling those seven products
-                    together and calling the bundle "Struts Classic". Instead,
-                    we are bundling Struts Action Framework and any compatible
-                    projects into a distribution called "Struts Action
-                    Framework Library". This bundle includes the original
-                    "seven dwarfs" and new subprojects, like Struts
-                    Scripting.</p>
             </answer>
         </faq>
+    </part>
+
+    <part>
+        <title>Project Details</title>
 
         <faq id="struts">
             <question>Why is the project called Struts?</question>
@@ -494,7 +516,6 @@
                 </p>
             </answer>
         </faq>
-
     </part>
 
     <part>



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