Author: asfgriff
Date: Thu Apr 25 19:31:30 2019
New Revision: 1858160

URL: http://svn.apache.org/viewvc?rev=1858160&view=rev
Log:
PLUTO-716 Committing site changes associated with the Pluto 3.1.0 release

Modified:
    portals/site/pluto/src/site/xdoc/v310/mvcbean-portlets.xml

Modified: portals/site/pluto/src/site/xdoc/v310/mvcbean-portlets.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/v310/mvcbean-portlets.xml?rev=1858160&r1=1858159&r2=1858160&view=diff
==============================================================================
--- portals/site/pluto/src/site/xdoc/v310/mvcbean-portlets.xml (original)
+++ portals/site/pluto/src/site/xdoc/v310/mvcbean-portlets.xml Thu Apr 25 
19:31:30 2019
@@ -30,7 +30,7 @@ limitations under the License.
                </section>
 
                <section name="MVC 1.0">
-                               <p>Portlet 3.0 introduced the concept of a CDI 
"bean portlet" and introduced annotation-driven method dispatching with 
annotations such as <code>@ActionMethod</code>, <code>@RenderMethod</code>, and 
<code>@ServeResourceMethod</code>. This is effectively the "C" (Controller) 
concern of the Model/View/Controller (MVC) design pattern.</p>
+                               <p>Portlet 3.0 introduced the concept of a CDI 
"bean portlet" featuring annotation-driven method dispatching with annotations 
such as <code>@ActionMethod</code>, <code>@RenderMethod</code>, and 
<code>@ServeResourceMethod</code>. This is effectively the "C" (Controller) 
concern of the Model/View/Controller (MVC) design pattern.</p>
                                <p>However, Portlet 3.0 did not provide the "M" 
(Model) or "V" (View) concerns, nor did it provide a CDI scope that allows for 
model data to survive from the <code>ACTION_PHASE</code> to the 
<code>RENDER_PHASE</code> of the portlet lifecycle.</p>
                                <p>In order to remedy this, Pluto implements 
MVC 1.0 in a way that makes sense for portlet development. Most of the 
requirements of MVC 1.0 are implemented; the main exception being those 
requirements that depend on JAX-RS for controller method dispatching. In other 
words, rather than using <code>@GET</code> and <code>@POST</code> from JAX-RS, 
MVCBean portlets rely on the aforementioned Portlet 3.0 annotations for 
controller method dispatching. Finally, Pluto implements MVC 1.0 
<code>@RedirectScoped</code> so that model data can survive from the 
<code>ACTION_PHASE</code> to the <code>RENDER_PHASE</code> of the portlet 
lifecycle.
                                </p>


Reply via email to