Author: asfgriff
Date: Thu Apr 25 19:30:09 2019
New Revision: 1858159
URL: http://svn.apache.org/viewvc?rev=1858159&view=rev
Log:
PLUTO-716 Committing site changes associated with the Pluto 3.1.0 release
Modified:
portals/site-live/pluto/v310/mvcbean-portlets.html
Modified: portals/site-live/pluto/v310/mvcbean-portlets.html
URL:
http://svn.apache.org/viewvc/portals/site-live/pluto/v310/mvcbean-portlets.html?rev=1858159&r1=1858158&r2=1858159&view=diff
==============================================================================
--- portals/site-live/pluto/v310/mvcbean-portlets.html (original)
+++ portals/site-live/pluto/v310/mvcbean-portlets.html Thu Apr 25 19:30:09 2019
@@ -124,7 +124,7 @@ Apache Pluto - MVCBean Portlets
<div class="section">
<h2><a name="MVC_1.0"></a>MVC 1.0</h2>
-<p>Portlet 3.0 introduced the concept of a CDI "bean portlet" and
introduced annotation-driven method dispatching with annotations such as
<tt>@ActionMethod</tt>, <tt>@RenderMethod</tt>, and
<tt>@ServeResourceMethod</tt>. 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
<tt>@ActionMethod</tt>, <tt>@RenderMethod</tt>, and
<tt>@ServeResourceMethod</tt>. 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 <tt>ACTION_PHASE</tt> to the
<tt>RENDER_PHASE</tt> of the portlet lifecycle.</p>
