Modified: portals/site-live/pluto/powered.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/powered.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/powered.html (original) +++ portals/site-live/pluto/powered.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="jetspeed-2/">Jetspeed-2</a> - | - <a href="bridges/">Bridges</a> - | - <a href="pluto/">Pluto</a> - | - <a href="applications/">Applications</a> - | - <a href="jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,82 +259,82 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Portal_using_Pluto"></a>Portal using Pluto</h2> -<p> - The following portals use Pluto for their portlet container: - <table class="bodyTable"><tr class="a"><th>Portal</th> -<th>Website</th> -<th>License</th> -<th>Status</th> -<th>Pluto Version</th> -</tr> -<tr class="b"><td>uPortal 3</td> -<td><a href="http://www.uportal.org"; class="externalLink">http://www.uportal.org</a></td> -<td>JA-SIG</td> -<td></td> -<td>1.1.x</td> -</tr> -<tr class="a"><td>Sakai</td> -<td><a href="http://www.sakaiproject.org"; class="externalLink">http://www.sakaiproject.org</a></td> -<td>Sakai Foundation</td> -<td></td> -<td>1.1.x</td> -</tr> -<tr class="b"><td>Apache Jetspeed 2</td> -<td><a href="http://portals.apache.org/jetspeed-2"; class="externalLink">http://portals.apache.org/jetspeed-2</a></td> -<td>Apache 2.0</td> -<td></td> -<td>2.0.0</td> -</tr> -<tr class="a"><td>Apache Cocoon</td> -<td><a href="http://cocoon.apache.org"; class="externalLink">http://cocoon.apache.org</a></td> -<td>Apache 2.0</td> -<td></td> -<td>1.0.1</td> -</tr> -<tr class="b"><td>uPortal 2</td> -<td><a href="http://www.uportal.org"; class="externalLink">http://www.uportal.org</a></td> -<td>JA-SIG</td> -<td></td> -<td>1.0.1</td> -</tr> -<tr class="a"><td>InfoGlue</td> -<td><a href="http://www.infoglue.org"; class="externalLink">http://www.infoglue.org</a></td> -<td>GPL</td> -<td></td> -<td>1.0.1</td> -</tr> -<tr class="b"><td>Jahia</td> -<td><a href="http://www.jahia.org"; class="externalLink">http://www.jahia.org</a></td> -<td><a href="http://www.collaborativesource.org"; class="externalLink">Proprietary</a></td> -<td>(http://www.jahia.org/cvs), branch JAHIA_PLUTO_BRANCH</td> -<td>1.0.1</td> -</tr> -</table> -</p> -<p> - The following applications utilize Pluto for providing Plugin Extensibility: - <table class="bodyTable"><tr class="a"><th>Portal</th> -<th>Website</th> -<th>License</th> -<th>Status</th> -<th>Pluto Version</th> -</tr> -<tr class="b"><td>Apache Geronimo </td> -<td><a href="http://geronimo.apache.org/"; class="externalLink">http://geronimo.apache.org</a></td> -<td>Apache 2.0</td> -<td>Web Management Console</td> -<td>1.1</td> -</tr> -<tr class="a"><td>Java Studio Creator 2.0</td> -<td><a href="http://developers.sun.com/prodtech/javatools/jscreator/"; class="externalLink">http://developers.sun.com/prodtech/javatools/jscreator/</a></td> -<td>Sun Microsystems Inc.</td> -<td>Development Portal Server</td> -<td>1.0.1</td> -</tr> -</table> -</p> -</div> + <div class="section"><h2><a name="Portal_using_Pluto"></a>Portal using Pluto</h2> +<p> + The following portals use Pluto for their portlet container: + <table class="bodyTable"><tr class="a"><th>Portal</th> +<th>Website</th> +<th>License</th> +<th>Status</th> +<th>Pluto Version</th> +</tr> +<tr class="b"><td>uPortal 3</td> +<td><a class="externalLink" href="http://www.uportal.org";>http://www.uportal.org</a></td> +<td>JA-SIG</td> +<td></td> +<td>1.1.x</td> +</tr> +<tr class="a"><td>Sakai</td> +<td><a class="externalLink" href="http://www.sakaiproject.org";>http://www.sakaiproject.org</a></td> +<td>Sakai Foundation</td> +<td></td> +<td>1.1.x</td> +</tr> +<tr class="b"><td>Apache Jetspeed 2</td> +<td><a class="externalLink" href="http://portals.apache.org/jetspeed-2";>http://portals.apache.org/jetspeed-2</a></td> +<td>Apache 2.0</td> +<td></td> +<td>2.0.0</td> +</tr> +<tr class="a"><td>Apache Cocoon</td> +<td><a class="externalLink" href="http://cocoon.apache.org";>http://cocoon.apache.org</a></td> +<td>Apache 2.0</td> +<td></td> +<td>1.0.1</td> +</tr> +<tr class="b"><td>uPortal 2</td> +<td><a class="externalLink" href="http://www.uportal.org";>http://www.uportal.org</a></td> +<td>JA-SIG</td> +<td></td> +<td>1.0.1</td> +</tr> +<tr class="a"><td>InfoGlue</td> +<td><a class="externalLink" href="http://www.infoglue.org";>http://www.infoglue.org</a></td> +<td>GPL</td> +<td></td> +<td>1.0.1</td> +</tr> +<tr class="b"><td>Jahia</td> +<td><a class="externalLink" href="http://www.jahia.org";>http://www.jahia.org</a></td> +<td><a class="externalLink" href="http://www.collaborativesource.org";>Proprietary</a></td> +<td>(http://www.jahia.org/cvs), branch JAHIA_PLUTO_BRANCH</td> +<td>1.0.1</td> +</tr> +</table> +</p> +<p> + The following applications utilize Pluto for providing Plugin Extensibility: + <table class="bodyTable"><tr class="a"><th>Portal</th> +<th>Website</th> +<th>License</th> +<th>Status</th> +<th>Pluto Version</th> +</tr> +<tr class="b"><td>Apache Geronimo </td> +<td><a class="externalLink" href="http://geronimo.apache.org/";>http://geronimo.apache.org</a></td> +<td>Apache 2.0</td> +<td>Web Management Console</td> +<td>1.1</td> +</tr> +<tr class="a"><td>Java Studio Creator 2.0</td> +<td><a class="externalLink" href="http://developers.sun.com/prodtech/javatools/jscreator/";>http://developers.sun.com/prodtech/javatools/jscreator/</a></td> +<td>Sun Microsystems Inc.</td> +<td>Development Portal Server</td> +<td>1.0.1</td> +</tr> +</table> +</p> +</div> </div> </div> @@ -353,7 +343,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation
Modified: portals/site-live/pluto/resources.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/resources.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/resources.html (original) +++ portals/site-live/pluto/resources.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="jetspeed-2/">Jetspeed-2</a> - | - <a href="bridges/">Bridges</a> - | - <a href="pluto/">Pluto</a> - | - <a href="applications/">Applications</a> - | - <a href="jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,56 +259,56 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="The_Java_Portlet_Specifications"></a>The Java Portlet Specifications</h2> -<p><ul><li><a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR-168: Portlet Specification 1.0</a></li> -<li><a href="http://jcp.org/en/jsr/detail?id=286"; class="externalLink">JSR-286: Portlet Specification 2.0</a></li> -</ul> -</p> -</div> -<div class="section"><h2><a name="Additional_Pluto_Documentation"></a>Additional Pluto Documentation</h2> -<p><ul><li><a href="http://wiki.apache.org/portals/Pluto"; class="externalLink">Official Pluto Wiki</a></li> -<li><a href="http://people.apache.org/~zheng/pluto/chinese/"; class="externalLink">Pluto - Website, Chinese Translation</a> maintained by ZHENG Zhong - </li> -</ul> -</p> -</div> -<div class="section"><h2><a name="Articles_Whitepapers_and_Presentations"></a>Articles, Whitepapers, and Presentations</h2> -<p><ul><li><a href="http://www.developer.com/java/web/article.php/3547186"; class="externalLink">Introduction to the Portlet Specification</a> - by David H. DeWolf, September 2005 - </li> -<li><a href="http://www.developer.com/java/web/article.php/3554396"; class="externalLink">Developing Portlets with Apache Pluto 1.1</a> - by David H. DeWolf, October 2005 - </li> -<li><a href="http://www.developer.com/java/web/article.php/3563411"; class="externalLink">Embedding Apache Pluto 1.1</a> - by David H. DeWolf, September 2005 - </li> -<li><a href="http://portletwork.blogspot.com/2007/08/testing-portlets-with-jetty-pluto-and.html"; class="externalLink"> - Testing Portlets with Jetty, Pluto and JWebUnit</a> - by Nils-Helge Garli, August 2007 - </li> -<li><a href="http://portletwork.blogspot.com/2007/07/mvnjetty-and-portlets.html"; class="externalLink"> - maven-jetty-plugin and JSR168 portlets</a> and - <a href="http://portletwork.blogspot.com/2007/08/maven-jetty-plugin-and-jsr168-portlets.html"; class="externalLink"> - maven-jetty-plugin and JSR168 portlets - Part 2</a> - by Nils-Helge Garli, August 2007 - </li> -</ul> -</p> -</div> -<div class="section"><h2><a name="Books"></a>Books</h2> -<p><ul><li><a href="http://www.manning.com/hepper/"; class="externalLink">Portlets and Apache Portals Book</a> a book from Portlet API specification authors and Pluto developers. - </li> -</ul> -</p> -</div> -<div class="section"><h2><a name="Other_Resources"></a>Other Resources</h2> -<p><ul><li><a href="http://code.google.com/p/pluto-server-plugin/"; class="externalLink">Pluto Server Plugin for Eclipse</a> - maintained by Marcus Christie - </li> -</ul> -</p> -</div> + <div class="section"><h2><a name="The_Java_Portlet_Specifications"></a>The Java Portlet Specifications</h2> +<p><ul><li><a class="externalLink" href="http://jcp.org/en/jsr/detail?id=168";>JSR-168: Portlet Specification 1.0</a></li> +<li><a class="externalLink" href="http://jcp.org/en/jsr/detail?id=286";>JSR-286: Portlet Specification 2.0</a></li> +</ul> +</p> +</div> +<div class="section"><h2><a name="Additional_Pluto_Documentation"></a>Additional Pluto Documentation</h2> +<p><ul><li><a class="externalLink" href="http://wiki.apache.org/portals/Pluto";>Official Pluto Wiki</a></li> +<li><a class="externalLink" href="http://people.apache.org/~zheng/pluto/chinese/";>Pluto + Website, Chinese Translation</a> maintained by ZHENG Zhong + </li> +</ul> +</p> +</div> +<div class="section"><h2><a name="Articles_Whitepapers_and_Presentations"></a>Articles, Whitepapers, and Presentations</h2> +<p><ul><li><a class="externalLink" href="http://www.developer.com/java/web/article.php/3547186";>Introduction to the Portlet Specification</a> + by David H. DeWolf, September 2005 + </li> +<li><a class="externalLink" href="http://www.developer.com/java/web/article.php/3554396";>Developing Portlets with Apache Pluto 1.1</a> + by David H. DeWolf, October 2005 + </li> +<li><a class="externalLink" href="http://www.developer.com/java/web/article.php/3563411";>Embedding Apache Pluto 1.1</a> + by David H. DeWolf, September 2005 + </li> +<li><a class="externalLink" href="http://portletwork.blogspot.com/2007/08/testing-portlets-with-jetty-pluto-and.html";> + Testing Portlets with Jetty, Pluto and JWebUnit</a> + by Nils-Helge Garli, August 2007 + </li> +<li><a class="externalLink" href="http://portletwork.blogspot.com/2007/07/mvnjetty-and-portlets.html";> + maven-jetty-plugin and JSR168 portlets</a> and + <a class="externalLink" href="http://portletwork.blogspot.com/2007/08/maven-jetty-plugin-and-jsr168-portlets.html";> + maven-jetty-plugin and JSR168 portlets - Part 2</a> + by Nils-Helge Garli, August 2007 + </li> +</ul> +</p> +</div> +<div class="section"><h2><a name="Books"></a>Books</h2> +<p><ul><li><a class="externalLink" href="http://www.manning.com/hepper/";>Portlets and Apache Portals Book</a> a book from Portlet API specification authors and Pluto developers. + </li> +</ul> +</p> +</div> +<div class="section"><h2><a name="Other_Resources"></a>Other Resources</h2> +<p><ul><li><a class="externalLink" href="http://code.google.com/p/pluto-server-plugin/";>Pluto Server Plugin for Eclipse</a> + maintained by Marcus Christie + </li> +</ul> +</p> +</div> </div> </div> @@ -327,7 +317,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/status.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/status.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/status.html (original) +++ portals/site-live/pluto/status.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="jetspeed-2/">Jetspeed-2</a> - | - <a href="bridges/">Bridges</a> - | - <a href="pluto/">Pluto</a> - | - <a href="applications/">Applications</a> - | - <a href="jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,39 +259,39 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Project_Status"></a>Project Status</h2> -<p> - Apache Pluto is a subproject of the Apache Portals Project. The current - stable release of Apache Pluto is version 2.0.3. Pluto 2.0 is both a Portlet Specification 2.0 (JSR-286) and Portlet Specification 1.0 (JSR-168) compliant implementation. - </p> -<div class="section"><h3><a name="Pluto_2.0"></a>Pluto 2.0</h3> -<p> - Pluto 2.0 is the current trunk of development and has an active development community. Version 2.0 has a new architecture and is a rewrite - of the Pluto 1.1 code-base. Pluto 2.0 is the reference implementation - of version 2.0 of the Java Portlet API specification (JSR-286). The JSR-286 - specification adds interportlet coordination (events and shared render parameters), - portlet filters and resource serving to the Portlet API in addition to - numerous other changes from version 1.0. However, Pluto 2.0 is also fully compliant to the 1.0 Portlet Specification. - Pluto 2.0, like Pluto 1.0.1, but unlike Pluto 1.1, runs inside the Jetspeed portal. Pluto 2.0 is embedded in Jetspeed 2.2.x versions, - whereas Pluto 1.0.1 is embedded in Jetspeed 2.1.x versions. - </p> -</div> -<div class="section"><h3><a name="Pluto_1.1"></a>Pluto 1.1</h3> -<p> - Pluto 1.1 introduced a new container architecture from version 1.0.1. If you are - embedding Pluto in your portal, realize that 1.1 is not binary - compatible with Pluto 1.0.x. Pluto 1.1 is no longer actively developed. Version 1.1 is only maintained for bug fixes in dependent portals. - </p> -</div> -<div class="section"><h3><a name="Pluto_1.0.1"></a>Pluto 1.0.1</h3> -<p> - Pluto 1.0.1 was the first stable release of Pluto. This version of - Pluto is utilized as the portlet container for Jetspeed and other - portals. In addition, Pluto 1.0.1 is embeded within Apache Geronimo. - Pluto 1.0.1 is no longer activily developed. 1.0.1 is only maintained for bug fixes in portals such as Jetspeed 2.1.x. - </p> -</div> -</div> + <div class="section"><h2><a name="Project_Status"></a>Project Status</h2> +<p> + Apache Pluto is a subproject of the Apache Portals Project. The current + stable release of Apache Pluto is version 2.0.3. Pluto 2.0 is both a Portlet Specification 2.0 (JSR-286) and Portlet Specification 1.0 (JSR-168) compliant implementation. + </p> +<div class="section"><h3><a name="Pluto_2.0"></a>Pluto 2.0</h3> +<p> + Pluto 2.0 is the current trunk of development and has an active development community. Version 2.0 has a new architecture and is a rewrite + of the Pluto 1.1 code-base. Pluto 2.0 is the reference implementation + of version 2.0 of the Java Portlet API specification (JSR-286). The JSR-286 + specification adds interportlet coordination (events and shared render parameters), + portlet filters and resource serving to the Portlet API in addition to + numerous other changes from version 1.0. However, Pluto 2.0 is also fully compliant to the 1.0 Portlet Specification. + Pluto 2.0, like Pluto 1.0.1, but unlike Pluto 1.1, runs inside the Jetspeed portal. Pluto 2.0 is embedded in Jetspeed 2.2.x versions, + whereas Pluto 1.0.1 is embedded in Jetspeed 2.1.x versions. + </p> +</div> +<div class="section"><h3><a name="Pluto_1.1"></a>Pluto 1.1</h3> +<p> + Pluto 1.1 introduced a new container architecture from version 1.0.1. If you are + embedding Pluto in your portal, realize that 1.1 is not binary + compatible with Pluto 1.0.x. Pluto 1.1 is no longer actively developed. Version 1.1 is only maintained for bug fixes in dependent portals. + </p> +</div> +<div class="section"><h3><a name="Pluto_1.0.1"></a>Pluto 1.0.1</h3> +<p> + Pluto 1.0.1 was the first stable release of Pluto. This version of + Pluto is utilized as the portlet container for Jetspeed and other + portals. In addition, Pluto 1.0.1 is embeded within Apache Geronimo. + Pluto 1.0.1 is no longer activily developed. 1.0.1 is only maintained for bug fixes in portals such as Jetspeed 2.1.x. + </p> +</div> +</div> </div> </div> @@ -310,7 +300,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/anttasks.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/anttasks.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/anttasks.html (original) +++ portals/site-live/pluto/subprojects/anttasks.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,39 +259,39 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Ant_Tasks"></a>Pluto Ant Tasks</h2> -<p> - The Pluto Ant Tasks have been created to assist those not using maven with the assembly, deployment, and publishing of Maven. A usage example is shown below: - </p> -<p><div class="source"><pre> - <path id="classes"> - <!-- - Pluto Ant Tasks depend upon the following libraries: - * pluto-ant-tasks-${version}.jar - * pluto-util-${version}.jar - * pluto-descriptor-api-${version}.jar - * pluto-descriptor-util-${version}.jar - * commons-logging-1.0.4.jar - * castor-1.1.1.jar - --> - <fileset dir="/path/to/pluto-libraries" includes="**/*.jar"/> - <fileset dir="/path/to/commons-logging" includes="**/*.jar"/> - <fileset dir="/path/to/castor" includes="**/*.jar"/> - </path> - - <typedef name="passemble" classname="org.apache.pluto.ant.AssembleTask" - classpathref="classes"/> - - <target name="passemble"> - <passemble - webxml="src/config/web.xml" - portletxml="src/config/portlet.xml" - destfile="src/webapp/WEB-INF/web.xml"/> - </target> - </pre> -</div> -</p> -</div> + <div class="section"><h2><a name="Pluto_Ant_Tasks"></a>Pluto Ant Tasks</h2> +<p> + The Pluto Ant Tasks have been created to assist those not using maven with the assembly, deployment, and publishing of Maven. A usage example is shown below: + </p> +<p><div class="source"><pre> + <path id="classes"> + <!-- + Pluto Ant Tasks depend upon the following libraries: + * pluto-ant-tasks-${version}.jar + * pluto-util-${version}.jar + * pluto-descriptor-api-${version}.jar + * pluto-descriptor-util-${version}.jar + * commons-logging-1.0.4.jar + * castor-1.1.1.jar + --> + <fileset dir="/path/to/pluto-libraries" includes="**/*.jar"/> + <fileset dir="/path/to/commons-logging" includes="**/*.jar"/> + <fileset dir="/path/to/castor" includes="**/*.jar"/> + </path> + + <typedef name="passemble" classname="org.apache.pluto.ant.AssembleTask" + classpathref="classes"/> + + <target name="passemble"> + <passemble + webxml="src/config/web.xml" + portletxml="src/config/portlet.xml" + destfile="src/webapp/WEB-INF/web.xml"/> + </target> + </pre> +</div> +</p> +</div> </div> </div> @@ -310,7 +300,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/container-api.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/container-api.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/container-api.html (original) +++ portals/site-live/pluto/subprojects/container-api.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,11 +259,11 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Container_API"></a>Pluto Container API</h2> -<p> - The Pluto Container API defines the container to portal interface. - </p> -</div> + <div class="section"><h2><a name="Pluto_Container_API"></a>Pluto Container API</h2> +<p> + The Pluto Container API defines the container to portal interface. + </p> +</div> </div> </div> @@ -282,7 +272,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/driver.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/driver.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/driver.html (original) +++ portals/site-live/pluto/subprojects/driver.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,11 +259,11 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Driver"></a>Pluto Driver</h2> -<p> - The Pluto Portal is a simple portal implementation. The Driver project includes common classes and interfaces for the Portal Implementation. It also contains the various portlets and tag libraries distributed in Pluto Portal. - </p> -</div> + <div class="section"><h2><a name="Pluto_Driver"></a>Pluto Driver</h2> +<p> + The Pluto Portal is a simple portal implementation. The Driver project includes common classes and interfaces for the Portal Implementation. It also contains the various portlets and tag libraries distributed in Pluto Portal. + </p> +</div> </div> </div> @@ -282,7 +272,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/installer.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/installer.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/installer.html (original) +++ portals/site-live/pluto/subprojects/installer.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,11 +259,11 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Installer"></a>Pluto Installer</h2> -<p> - The Pluto Installer is a Maven Plugin. - </p> -</div> + <div class="section"><h2><a name="Pluto_Installer"></a>Pluto Installer</h2> +<p> + The Pluto Installer is a Maven Plugin. + </p> +</div> </div> </div> @@ -282,7 +272,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/portal.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/portal.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/portal.html (original) +++ portals/site-live/pluto/subprojects/portal.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,11 +259,11 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Portal"></a>Pluto Portal</h2> -<p> - The Pluto Portal web application is the skeleton structure for the Pluto Portal. It includes resources (CSS, graphics), source JSPs, and configuration (.properties, .xml) files. - </p> -</div> + <div class="section"><h2><a name="Pluto_Portal"></a>Pluto Portal</h2> +<p> + The Pluto Portal web application is the skeleton structure for the Pluto Portal. It includes resources (CSS, graphics), source JSPs, and configuration (.properties, .xml) files. + </p> +</div> </div> </div> @@ -282,7 +272,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/portlet-container.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/portlet-container.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/portlet-container.html (original) +++ portals/site-live/pluto/subprojects/portlet-container.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,16 +259,16 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Portlet_Container"></a>Pluto Portlet Container</h2> -<p> - The Pluto Portlet Container is not designed for use by end users. - The container is meant to be embedded within portal and web applications to provide Java Portlet Specification compliance. - If you are a user looking to develop, test, or deploy portlets, please see the Pluto Portal Driver . - </p> -<p> -If you are looking for information on how to embed pluto in your portal or web application, please see the <a href="v20/embedding.html">embedding</a> pluto documentation for Pluto 2.0. - </p> -</div> + <div class="section"><h2><a name="Pluto_Portlet_Container"></a>Pluto Portlet Container</h2> +<p> + The Pluto Portlet Container is not designed for use by end users. + The container is meant to be embedded within portal and web applications to provide Java Portlet Specification compliance. + If you are a user looking to develop, test, or deploy portlets, please see the Pluto Portal Driver . + </p> +<p> +If you are looking for information on how to embed pluto in your portal or web application, please see the <a href="v20/embedding.html">embedding</a> pluto documentation for Pluto 2.0. + </p> +</div> </div> </div> @@ -287,7 +277,7 @@ If you are looking for information on ho </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/skin.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/skin.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/skin.html (original) +++ portals/site-live/pluto/subprojects/skin.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,11 +259,11 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Skin_for_Maven"></a>Pluto Skin for Maven</h2> -<p> - Contains resources (CSS, images) for this website. - </p> -</div> + <div class="section"><h2><a name="Pluto_Skin_for_Maven"></a>Pluto Skin for Maven</h2> +<p> + Contains resources (CSS, images) for this website. + </p> +</div> </div> </div> @@ -282,7 +272,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/subprojects.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/subprojects.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/subprojects.html (original) +++ portals/site-live/pluto/subprojects/subprojects.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,82 +259,82 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Subprojects"></a>Pluto Subprojects</h2> -<p> - Pluto 2.0 utilizes Maven 2 as it's project management and build - automation tool. Pluto follows maven's best practices and is organized - into modules or subprojects. - </p> -<div class="section"><h3><a name="Container_Subprojects"></a>Container Subprojects</h3> -<p><ul><li><b>Pluto Container:</b> - The Pluto Container is the core compontent of the Apache Pluto - project. All other modules either support the development. The - Pluto Container is the reference implementation of the Portlet - Specification. - </li> -<li><b>Pluto Tags:</b> - The Java Portlet Tag Library implementation which is provided - with the container. - </li> -</ul> -</p> -</div> -<div class="section"><h3><a name="PortalTesting_Subprojects"></a>Portal/Testing Subprojects</h3> -<p><ul><li><b>Pluto Portal Driver:</b> - A driver library for the Pluto Portlet Container. Provides service - implementations and utilities for implementing a portal which - utilizes the container. - </li> -<li><b>Pluto Portal:</b> - The user interface components (web application) of the Pluto - Portal. The pluto portal is a simple portal application which - embeds the portal. The portal is not meant to be a full enterprise - portal, but instead is meant to be an example of how to embed the - container and a lightweight environment for developing and testing - portlets. - </li> -<li><b>Pluto Testsuite:</b> - A test portlet which can be used to exercise and test any portlet - container. - </li> -</ul> -</p> -</div> -<div class="section"><h3><a name="Libraries_and_Supporting_Subprojects"></a>Libraries and Supporting Subprojects</h3> -<p><ul><li><b>Pluto Descriptor API:</b> - A domain model which represents the deployment descriptors read - by the portlet container. Contains service interfaces for reading - and writing portlet.xml and web.xml. - </li> -<li><b>Pluto Descriptor Impl:</b> - The default implementation of the Pluto Descriptor API Subproject. - The default implementation utilzes castor for reading and writing - portlet and web application descriptors. - </li> -</ul> -</p> -</div> -<div class="section"><h3><a name="Utilities_and_Tools_for_working_with_the_Pluto_Portal"></a>Utilities and Tools (for working with the Pluto Portal)</h3> -<p><ul><li><b>Pluto Util:</b> - Utilities for working with the Pluto Portal. Includes libraries - for installing pluto, assembling portlet applications for - deployment in pluto, deploying to pluto, and publishing portlets - to pluto. - </li> -<li><b>Maven Plugin:</b> - Provides Maven goals for utilizing the Pluto utilities. Install - the portal within a servlet container, assemble portlets, deploy - portlets, and publish portlets to th Pluto Portal. - </li> -<li><b>Ant Tasks:</b> - Ant tasks which allow developers to utilize the Pluto utilities - within ant. Currently supports assembling wars for deployment - within pluto. - </li> -</ul> -</p> -</div> -</div> + <div class="section"><h2><a name="Pluto_Subprojects"></a>Pluto Subprojects</h2> +<p> + Pluto 2.0 utilizes Maven 2 as it's project management and build + automation tool. Pluto follows maven's best practices and is organized + into modules or subprojects. + </p> +<div class="section"><h3><a name="Container_Subprojects"></a>Container Subprojects</h3> +<p><ul><li><b>Pluto Container:</b> + The Pluto Container is the core compontent of the Apache Pluto + project. All other modules either support the development. The + Pluto Container is the reference implementation of the Portlet + Specification. + </li> +<li><b>Pluto Tags:</b> + The Java Portlet Tag Library implementation which is provided + with the container. + </li> +</ul> +</p> +</div> +<div class="section"><h3><a name="PortalTesting_Subprojects"></a>Portal/Testing Subprojects</h3> +<p><ul><li><b>Pluto Portal Driver:</b> + A driver library for the Pluto Portlet Container. Provides service + implementations and utilities for implementing a portal which + utilizes the container. + </li> +<li><b>Pluto Portal:</b> + The user interface components (web application) of the Pluto + Portal. The pluto portal is a simple portal application which + embeds the portal. The portal is not meant to be a full enterprise + portal, but instead is meant to be an example of how to embed the + container and a lightweight environment for developing and testing + portlets. + </li> +<li><b>Pluto Testsuite:</b> + A test portlet which can be used to exercise and test any portlet + container. + </li> +</ul> +</p> +</div> +<div class="section"><h3><a name="Libraries_and_Supporting_Subprojects"></a>Libraries and Supporting Subprojects</h3> +<p><ul><li><b>Pluto Descriptor API:</b> + A domain model which represents the deployment descriptors read + by the portlet container. Contains service interfaces for reading + and writing portlet.xml and web.xml. + </li> +<li><b>Pluto Descriptor Impl:</b> + The default implementation of the Pluto Descriptor API Subproject. + The default implementation utilzes castor for reading and writing + portlet and web application descriptors. + </li> +</ul> +</p> +</div> +<div class="section"><h3><a name="Utilities_and_Tools_for_working_with_the_Pluto_Portal"></a>Utilities and Tools (for working with the Pluto Portal)</h3> +<p><ul><li><b>Pluto Util:</b> + Utilities for working with the Pluto Portal. Includes libraries + for installing pluto, assembling portlet applications for + deployment in pluto, deploying to pluto, and publishing portlets + to pluto. + </li> +<li><b>Maven Plugin:</b> + Provides Maven goals for utilizing the Pluto utilities. Install + the portal within a servlet container, assemble portlets, deploy + portlets, and publish portlets to th Pluto Portal. + </li> +<li><b>Ant Tasks:</b> + Ant tasks which allow developers to utilize the Pluto utilities + within ant. Currently supports assembling wars for deployment + within pluto. + </li> +</ul> +</p> +</div> +</div> </div> </div> @@ -353,7 +343,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/tag-library.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/tag-library.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/tag-library.html (original) +++ portals/site-live/pluto/subprojects/tag-library.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,11 +259,11 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Tag_Library"></a>Pluto Tag Library</h2> -<p> - Contains the tags used by Pluto Portal. - </p> -</div> + <div class="section"><h2><a name="Pluto_Tag_Library"></a>Pluto Tag Library</h2> +<p> + Contains the tags used by Pluto Portal. + </p> +</div> </div> </div> @@ -282,7 +272,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/testsuite.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/testsuite.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/testsuite.html (original) +++ portals/site-live/pluto/subprojects/testsuite.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,11 +259,11 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Test_Suite"></a>Pluto Test Suite</h2> -<p> - The Pluto testsuite is comprised of multiple portlets meant to be deployed in the portal to be tested. Portals wanting to embed Pluto can use the testsuite to test the correctness of their integration. - </p> -</div> + <div class="section"><h2><a name="Pluto_Test_Suite"></a>Pluto Test Suite</h2> +<p> + The Pluto testsuite is comprised of multiple portlets meant to be deployed in the portal to be tested. Portals wanting to embed Pluto can use the testsuite to test the correctness of their integration. + </p> +</div> </div> </div> @@ -282,7 +272,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/subprojects/utilities.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/subprojects/utilities.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/subprojects/utilities.html (original) +++ portals/site-live/pluto/subprojects/utilities.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../jetspeed-2/">Jetspeed-2</a> - | - <a href="../bridges/">Bridges</a> - | - <a href="../pluto/">Pluto</a> - | - <a href="../applications/">Applications</a> - | - <a href="../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,11 +259,11 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Utilities"></a>Pluto Utilities</h2> -<p> - The utilities project includes the Pluto Assembler and Pluto Installer. - </p> -</div> + <div class="section"><h2><a name="Pluto_Utilities"></a>Pluto Utilities</h2> +<p> + The utilities project includes the Pluto Assembler and Pluto Installer. + </p> +</div> </div> </div> @@ -282,7 +272,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/v101/developer/arch.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v101/developer/arch.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/v101/developer/arch.html (original) +++ portals/site-live/pluto/v101/developer/arch.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../../jetspeed-2/">Jetspeed-2</a> - | - <a href="../../bridges/">Bridges</a> - | - <a href="../../pluto/">Pluto</a> - | - <a href="../../applications/">Applications</a> - | - <a href="../../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,113 +259,113 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Architecture_Overview"></a>Architecture Overview</h2> -<p> - Let's begin by examining Pluto's architecture and underlying concepts. - First, we briefly explain the portal that runs the RI, and see where - to find a portlet container inside a portal architecture. Next, we - investigate Pluto's architecture in detail. Last, we look at how it - solves one challenging item of the portlet container: portlet deployment. -</p> -<p><strong>The Portal</strong><blockquote> - Pluto normally serves to show how the Portlet API works and - offers developers a working example platform from which they can test - their portlets. However, it's cumbersome to execute and test the portlet - container without a driver, in this case, the portal. Pluto's simple - portal component is built only on the portlet container's and the JSR - 168's requirements. (In contrast, the more sophisticated, open source - Apache Jetspeed project concentrates on the portal itself rather than - the portlet container, and considers requirements from other groups.) - </blockquote><blockquote> - Figure 1 depicts the portal's basic architecture. The portal Web - application processes the client request, retrieves the portlets on - the user's current page, and then calls the portlet container to - retrieve each portlet's content. The portal accesses the portlet - container with the Portlet Container Invoker API, representing the - portlet container's main interface supporting request-based methods - to call portlets from a portal's viewpoint. The container's user must - implement the portlet container's Container Provider SPI (Service - Provider Interface) callback interface to get portal-related - information. Finally, the portlet container calls all portlets - via the Portlet API. - </blockquote><blockquote><div align="center"><p><a href="../../images/v101/jw-0801-portal_arch.jpg"><img src="../../images/v101/jw-0801-portal_arch.jpg" alt="Portal Architecture" /></a></p> -<p><b><i><font size="-1">Figure 1. The simple portal included with Pluto. Click on the picture to enlarge it</font></i></b></p> -</div></blockquote></p> -<p><strong>The Portlet Container</strong><blockquote> - The portlet container, the portlets' runtime environment and a core - component of each portal, requires knowledge about the portal itself - and must reuse common code from it. Consequently, the portlet - container remains completely separated from every other portal component. - That said, you can embed the standalone portlet container in any portal - by complying with the portlet container's requirements, such as - implementing all SPIs. - </blockquote><blockquote> - The Portlet Container Invoker API, also called an entrance point, acts - as the portlet container's main calling interface. The API combines a - portlet container's lifecycle (init, destroy) with request-based - calling methods (initPage(), performTitle(), portletService(), and so - on). Because the portlet container calls a portlet in the end, the - method signature resembles the Portlet API's main portlet interface, - except that a portlet identifier must be passed. With this additional - portlet identifier, the container can determine the portlet and call - it accordingly. - </blockquote><blockquote> - Besides using the APIs to access the portlet container, the portal - must implement SPIs defined for the portlet container. Therefore, - the RI introduces container services: pluggable components that can - be registered at the container to either extend or provide basic - functionality. The RI includes the following built-in container services - (the first four must be implemented to run the portlet container, while - the fifth is optional): - </blockquote><blockquote><ul><li> Information provider: Gives the portlet container information about - the portal and its framework. Only known information or information - that should be stored within the portal is present through this - interface. Such information includes URL generation with navigational - state, portlet context, portlet mode, and window-state handling</li> -<li> Factory manager: Defines how to get an implementation through a - factory. (A normal portal should already own such an implementation.)</li> -<li> Log service: Defines a logging facility. (A normal portal should - already own such an implementation.)</li> -<li> Config service: Defines how to get configuration values. (A normal portal - should already own such an implementation.)</li> -<li> Property manager (optional): A property manager interface implementation - lets a portal handle properties as defined in the JSR 168 specification.</li> -</ul> -</blockquote><blockquote> - Strictly speaking, the Portlet Object Model also acts as an SPI, but has an - exceptional position among the SPIs. Therefore, don't consider it part of the - container services as it deals with all portlet objects and comprises a collection - of interwoven interfaces. - </blockquote><blockquote><div align="center"><p><a href="../../images/v101/jw-0801-pluto_arch.jpg"><img src="../../images/v101/jw-0801-pluto_arch.jpg" alt="Pluto Architecture" /></a></p> -<p><b><i><font size="-1">Figure 2. The portlet container's architecture. Click on the picture to enlarge it</font></i></b></p> -</div></blockquote></p> -<p><strong>Portlet Deployment</strong><blockquote> - The portlet container can leverage the servlet container's functionality, upon - which the portlet container is built. To accomplish that, the portlet container - must inject servlet artifacts into each portlet-application war file, as Figure - 3 shows. The portlet component, Deployment, takes the original war file, then - injects a new or modified web.xml and a servlet to wrap each portlet and uses - it as a calling point. Then the portlet deployment passes the modified war - file to the application server deployment, which deploys it into the - application server's system. During the portlet's invocation, the portlet - container calls the injected servlet as an entrance point into the deployed - portlet war file. - </blockquote><blockquote><div align="center"><p><a href="../../images/v101/jw-0801-RI_deploy.jpg"><img src="../../images/v101/jw-0801-RI_deploy.jpg" alt="Deployment" /></a></p> -<p><b><i><font size="-1">Figure 3. Portlet deployment in the RI. Click on thumbnail to view full-size image.</font></i></b></p> -</div></blockquote></p> -<p><strong>Pluto and the WSRP standard</strong><blockquote> - The JSR 168 aligns closely with the Web Services for Remote Portlets (WSRP) standard. - Both standards, which emerged at the same time, released open source implementations - capable of all necessary functions described in the respective specifications. - As a mutual goal, both standards strive to work well together. As a result, - the portlet container can run WSRP portlets as a consumer as well as a producer. - </blockquote><blockquote> - Pluto must be able to run multiple portlet containers in one portal. Consequently, - Pluto's portlet container can be instantiated multiple times and, more importantly, - it can be instrumented in different ways. Each portlet container, therefore, can - use different implementations for SPIs. - </blockquote></p> -</div> + <div class="section"><h2><a name="Architecture_Overview"></a>Architecture Overview</h2> +<p> + Let's begin by examining Pluto's architecture and underlying concepts. + First, we briefly explain the portal that runs the RI, and see where + to find a portlet container inside a portal architecture. Next, we + investigate Pluto's architecture in detail. Last, we look at how it + solves one challenging item of the portlet container: portlet deployment. +</p> +<p><strong>The Portal</strong><blockquote> + Pluto normally serves to show how the Portlet API works and + offers developers a working example platform from which they can test + their portlets. However, it's cumbersome to execute and test the portlet + container without a driver, in this case, the portal. Pluto's simple + portal component is built only on the portlet container's and the JSR + 168's requirements. (In contrast, the more sophisticated, open source + Apache Jetspeed project concentrates on the portal itself rather than + the portlet container, and considers requirements from other groups.) + </blockquote><blockquote> + Figure 1 depicts the portal's basic architecture. The portal Web + application processes the client request, retrieves the portlets on + the user's current page, and then calls the portlet container to + retrieve each portlet's content. The portal accesses the portlet + container with the Portlet Container Invoker API, representing the + portlet container's main interface supporting request-based methods + to call portlets from a portal's viewpoint. The container's user must + implement the portlet container's Container Provider SPI (Service + Provider Interface) callback interface to get portal-related + information. Finally, the portlet container calls all portlets + via the Portlet API. + </blockquote><blockquote><div align="center"><p><a href="../../images/v101/jw-0801-portal_arch.jpg"><img src="../../images/v101/jw-0801-portal_arch.jpg" alt="Portal Architecture" /></a></p> +<p><b><i><font size="-1">Figure 1. The simple portal included with Pluto. Click on the picture to enlarge it</font></i></b></p> +</div></blockquote></p> +<p><strong>The Portlet Container</strong><blockquote> + The portlet container, the portlets' runtime environment and a core + component of each portal, requires knowledge about the portal itself + and must reuse common code from it. Consequently, the portlet + container remains completely separated from every other portal component. + That said, you can embed the standalone portlet container in any portal + by complying with the portlet container's requirements, such as + implementing all SPIs. + </blockquote><blockquote> + The Portlet Container Invoker API, also called an entrance point, acts + as the portlet container's main calling interface. The API combines a + portlet container's lifecycle (init, destroy) with request-based + calling methods (initPage(), performTitle(), portletService(), and so + on). Because the portlet container calls a portlet in the end, the + method signature resembles the Portlet API's main portlet interface, + except that a portlet identifier must be passed. With this additional + portlet identifier, the container can determine the portlet and call + it accordingly. + </blockquote><blockquote> + Besides using the APIs to access the portlet container, the portal + must implement SPIs defined for the portlet container. Therefore, + the RI introduces container services: pluggable components that can + be registered at the container to either extend or provide basic + functionality. The RI includes the following built-in container services + (the first four must be implemented to run the portlet container, while + the fifth is optional): + </blockquote><blockquote><ul><li> Information provider: Gives the portlet container information about + the portal and its framework. Only known information or information + that should be stored within the portal is present through this + interface. Such information includes URL generation with navigational + state, portlet context, portlet mode, and window-state handling</li> +<li> Factory manager: Defines how to get an implementation through a + factory. (A normal portal should already own such an implementation.)</li> +<li> Log service: Defines a logging facility. (A normal portal should + already own such an implementation.)</li> +<li> Config service: Defines how to get configuration values. (A normal portal + should already own such an implementation.)</li> +<li> Property manager (optional): A property manager interface implementation + lets a portal handle properties as defined in the JSR 168 specification.</li> +</ul> +</blockquote><blockquote> + Strictly speaking, the Portlet Object Model also acts as an SPI, but has an + exceptional position among the SPIs. Therefore, don't consider it part of the + container services as it deals with all portlet objects and comprises a collection + of interwoven interfaces. + </blockquote><blockquote><div align="center"><p><a href="../../images/v101/jw-0801-pluto_arch.jpg"><img src="../../images/v101/jw-0801-pluto_arch.jpg" alt="Pluto Architecture" /></a></p> +<p><b><i><font size="-1">Figure 2. The portlet container's architecture. Click on the picture to enlarge it</font></i></b></p> +</div></blockquote></p> +<p><strong>Portlet Deployment</strong><blockquote> + The portlet container can leverage the servlet container's functionality, upon + which the portlet container is built. To accomplish that, the portlet container + must inject servlet artifacts into each portlet-application war file, as Figure + 3 shows. The portlet component, Deployment, takes the original war file, then + injects a new or modified web.xml and a servlet to wrap each portlet and uses + it as a calling point. Then the portlet deployment passes the modified war + file to the application server deployment, which deploys it into the + application server's system. During the portlet's invocation, the portlet + container calls the injected servlet as an entrance point into the deployed + portlet war file. + </blockquote><blockquote><div align="center"><p><a href="../../images/v101/jw-0801-RI_deploy.jpg"><img src="../../images/v101/jw-0801-RI_deploy.jpg" alt="Deployment" /></a></p> +<p><b><i><font size="-1">Figure 3. Portlet deployment in the RI. Click on thumbnail to view full-size image.</font></i></b></p> +</div></blockquote></p> +<p><strong>Pluto and the WSRP standard</strong><blockquote> + The JSR 168 aligns closely with the Web Services for Remote Portlets (WSRP) standard. + Both standards, which emerged at the same time, released open source implementations + capable of all necessary functions described in the respective specifications. + As a mutual goal, both standards strive to work well together. As a result, + the portlet container can run WSRP portlets as a consumer as well as a producer. + </blockquote><blockquote> + Pluto must be able to run multiple portlet containers in one portal. Consequently, + Pluto's portlet container can be instantiated multiple times and, more importantly, + it can be instrumented in different ways. Each portlet container, therefore, can + use different implementations for SPIs. + </blockquote></p> +</div> </div> </div> @@ -384,7 +374,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/v101/developer/build_source.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v101/developer/build_source.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/v101/developer/build_source.html (original) +++ portals/site-live/pluto/v101/developer/build_source.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../../jetspeed-2/">Jetspeed-2</a> - | - <a href="../../bridges/">Bridges</a> - | - <a href="../../pluto/">Pluto</a> - | - <a href="../../applications/">Applications</a> - | - <a href="../../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,86 +259,86 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Installation"></a>Installation</h2> -<div class="section"><h3><a name="Prerequisites"></a>Prerequisites</h3> -<p>It is expected that the user is familiar with the <a href="http://maven.apache.org"; class="externalLink">Apache - Maven</a> project tool.</p> -</div> -<div class="section"><h3><a name="Requirements"></a>Requirements</h3> -<ul><li><a href="http://maven.apache.org/start/download.html"; class="externalLink">Maven 1.0.2</a></li> -<li>Java 1.4 or higher (If using JDK 1.4 in Tomcat 5.5, see Running.txt in Tomcat's home directory for modification instructions)</li> -<li>Servlet 2.3 compatible container: Tomcat 5.5 is suggested</li> -</ul> -</div> -<div class="section"><h3><a name="Get_Maven_Ready"></a>Get Maven Ready</h3> -<p>If you have not already done so, download and install Maven.</p> -<p>2. build.properties settings:</p> -<p>Please set these values in your <code>build.properties</code> - file:</p> -<table class="bodyTable"><tr class="a"><th width="134">property</th> -<th width="229">example</th> -<th width="261">what is it?</th> -</tr> -<tr class="b"><td width="134">maven.tomcat.home</td> -<td width="229">/tomcat</td> -<td width="261">location of the Tomcat install where you want to deploy Pluto</td> -</tr> -<tr class="a"><td width="134">maven.tomcat.version.major</td> -<td width="229">5</td> -<td width="261">Major version of Tomcat</td> -</tr> -</table> -<p>You can copy the <code>build.properties.sample</code> file and name it - <code>build.properties</code> and use this is a starting point.</p> -</div> -<div class="section"><h3><a name="Building_and_deploying"></a>Building and deploying</h3> -<ul><li>change your directory to root of the Pluto project.</li> -<li>maven fullDeployment</li> -<li>This will take care of everything for you including copying shared jars, - and deploy the base Pluto portal along with the Portlet Test Suite</li> -</ul> -</div> -<div class="section"><h3><a name="Start_Tomcat"></a>Start Tomcat</h3> -<p>Run Tomcat, go to http://localhost:8080/pluto/portal.</p> -</div> -</div> -<div class="section"><h2><a name="What_if_I_just_want_the_Pluto_container_jar_like_for_Jetspeed_2"></a>What if I just want the Pluto container jar (like for Jetspeed 2)?</h2> -<ol type="1"><li>cd to /container directory</li> -<li>maven jar:install</li> -</ol> -<p>This will create the container jar in /container/target and also copy into - you maven repository.</p> -</div> -<div class="section"><h2><a name="What_if_I_just_want_to_deploy_the_Pluto_portal_without_the_test_suite"></a>What if I just want to deploy the Pluto portal without the test suite?</h2> -<ol type="1"><li>Follow all the steps from "<i>What if I just want the Pluto container - jar (like for Jetspeed 2)?</i>"</li> -<li>cd to the /portal directory.</li> -<li>maven (with no goal)</li> -</ol> -<p>This will invoke the default maven goal for the /portal sub-project, tomcat:deploy. - This will build and deploy the Pluto portal minus the test suite into - tomcat.</p> -</div> -<div class="section"><h2><a name="What_if_I_decide_I_want_to_deploy_the_test_suite_portlets_after_I_deploy_the_Pluto_portal_by_itself"></a>What if I decide I want to deploy the test suite portlets after I deploy the Pluto portal by itself?</h2> -<ol type="1"><li>Follow all the steps from "<i>What if I decide I want to deploy the - test suite portlets after I deploy JUST the Pluto portal?</i>"</li> -<li>cd to the /testsuite directory.</li> -<li>maven (with no goal)</li> -</ol> -<p>This will invoke the default maven goal for the /testsute sub-project, deployTestsuite. - This will build and deploy the test suite portlets into your already deployed - Pluto portal.</p> -</div> -<div class="section"><h2><a name="Install_Portlets"></a>Install Portlets</h2> -<p><ul>To install portlets after you successfully installed Pluto, - invoke Maven from the deploy subdirectory of the base install directory to deploy the portlet's war by executing:<br /> -<code>maven deploy -Ddeploy=FULL_PATH_TO_YOUR_PORTLET_WAR</code><br /> - - Alternatively, you could use the <a href="../install.html#Admin_Portlet_Application">Admin Portlet Application</a> - to install custom portlets. - </ul> -</p> -</div> + <div class="section"><h2><a name="Installation"></a>Installation</h2> +<div class="section"><h3><a name="Prerequisites"></a>Prerequisites</h3> +<p>It is expected that the user is familiar with the <a class="externalLink" href="http://maven.apache.org";>Apache + Maven</a> project tool.</p> +</div> +<div class="section"><h3><a name="Requirements"></a>Requirements</h3> +<ul><li><a class="externalLink" href="http://maven.apache.org/start/download.html";>Maven 1.0.2</a></li> +<li>Java 1.4 or higher (If using JDK 1.4 in Tomcat 5.5, see Running.txt in Tomcat's home directory for modification instructions)</li> +<li>Servlet 2.3 compatible container: Tomcat 5.5 is suggested</li> +</ul> +</div> +<div class="section"><h3><a name="Get_Maven_Ready"></a>Get Maven Ready</h3> +<p>If you have not already done so, download and install Maven.</p> +<p>2. build.properties settings:</p> +<p>Please set these values in your <code>build.properties</code> + file:</p> +<table class="bodyTable"><tr class="a"><th width="134">property</th> +<th width="229">example</th> +<th width="261">what is it?</th> +</tr> +<tr class="b"><td width="134">maven.tomcat.home</td> +<td width="229">/tomcat</td> +<td width="261">location of the Tomcat install where you want to deploy Pluto</td> +</tr> +<tr class="a"><td width="134">maven.tomcat.version.major</td> +<td width="229">5</td> +<td width="261">Major version of Tomcat</td> +</tr> +</table> +<p>You can copy the <code>build.properties.sample</code> file and name it + <code>build.properties</code> and use this is a starting point.</p> +</div> +<div class="section"><h3><a name="Building_and_deploying"></a>Building and deploying</h3> +<ul><li>change your directory to root of the Pluto project.</li> +<li>maven fullDeployment</li> +<li>This will take care of everything for you including copying shared jars, + and deploy the base Pluto portal along with the Portlet Test Suite</li> +</ul> +</div> +<div class="section"><h3><a name="Start_Tomcat"></a>Start Tomcat</h3> +<p>Run Tomcat, go to http://localhost:8080/pluto/portal.</p> +</div> +</div> +<div class="section"><h2><a name="What_if_I_just_want_the_Pluto_container_jar_like_for_Jetspeed_2"></a>What if I just want the Pluto container jar (like for Jetspeed 2)?</h2> +<ol type="1"><li>cd to /container directory</li> +<li>maven jar:install</li> +</ol> +<p>This will create the container jar in /container/target and also copy into + you maven repository.</p> +</div> +<div class="section"><h2><a name="What_if_I_just_want_to_deploy_the_Pluto_portal_without_the_test_suite"></a>What if I just want to deploy the Pluto portal without the test suite?</h2> +<ol type="1"><li>Follow all the steps from "<i>What if I just want the Pluto container + jar (like for Jetspeed 2)?</i>"</li> +<li>cd to the /portal directory.</li> +<li>maven (with no goal)</li> +</ol> +<p>This will invoke the default maven goal for the /portal sub-project, tomcat:deploy. + This will build and deploy the Pluto portal minus the test suite into + tomcat.</p> +</div> +<div class="section"><h2><a name="What_if_I_decide_I_want_to_deploy_the_test_suite_portlets_after_I_deploy_the_Pluto_portal_by_itself"></a>What if I decide I want to deploy the test suite portlets after I deploy the Pluto portal by itself?</h2> +<ol type="1"><li>Follow all the steps from "<i>What if I decide I want to deploy the + test suite portlets after I deploy JUST the Pluto portal?</i>"</li> +<li>cd to the /testsuite directory.</li> +<li>maven (with no goal)</li> +</ol> +<p>This will invoke the default maven goal for the /testsute sub-project, deployTestsuite. + This will build and deploy the test suite portlets into your already deployed + Pluto portal.</p> +</div> +<div class="section"><h2><a name="Install_Portlets"></a>Install Portlets</h2> +<p><ul>To install portlets after you successfully installed Pluto, + invoke Maven from the deploy subdirectory of the base install directory to deploy the portlet's war by executing:<br /> +<code>maven deploy -Ddeploy=FULL_PATH_TO_YOUR_PORTLET_WAR</code><br /> + + Alternatively, you could use the <a href="../install.html#Admin_Portlet_Application">Admin Portlet Application</a> + to install custom portlets. + </ul> +</p> +</div> </div> </div> @@ -357,7 +347,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation Modified: portals/site-live/pluto/v101/developer/index.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v101/developer/index.html?rev=1772018&r1=1772017&r2=1772018&view=diff ============================================================================== --- portals/site-live/pluto/v101/developer/index.html (original) +++ portals/site-live/pluto/v101/developer/index.html Wed Nov 30 12:21:20 2016 @@ -47,21 +47,11 @@ <div class="xleft"> - Last Published: 2011-09-26 + Last Published: 2016-11-30 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> - <div class="xright"> <a href="../../jetspeed-2/">Jetspeed-2</a> - | - <a href="../../bridges/">Bridges</a> - | - <a href="../../pluto/">Pluto</a> - | - <a href="../../applications/">Applications</a> - | - <a href="../../jetspeed-1/">Jetspeed-1</a> - | - <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> + <div class="xright"> <a href="http://jcp.org/en/jsr/detail?id=168"; class="externalLink">JSR 168 (Portlet 1.0)</a> | <a href="http://portals.apache.org/pluto/portlet-1.0-apidocs"; class="externalLink">Portlet 1.0 API (Javadoc)</a> | @@ -269,8 +259,8 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_Developer_Guide"></a>Pluto Developer Guide</h2> -</div> + <div class="section"><h2><a name="Pluto_Developer_Guide"></a>Pluto Developer Guide</h2> +</div> </div> </div> @@ -279,7 +269,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2011 + 2004-2016 Apache Software Foundation
