Author: msnicklous
Date: Thu Dec 1 09:12:16 2016
New Revision: 1772163
URL: http://svn.apache.org/viewvc?rev=1772163&view=rev
Log:
Modified site structure to reorganize some links
Modified:
portals/site/pluto/src/site/site.xml
portals/site/pluto/src/site/xdoc/index.xml
Modified: portals/site/pluto/src/site/site.xml
URL: http://svn.apache.org/viewvc/portals/site/pluto/src/site/site.xml?rev=1772163&r1=1772162&r2=1772163&view=diff
==============================================================================
--- portals/site/pluto/src/site/site.xml (original)
+++ portals/site/pluto/src/site/site.xml Thu Dec 1 09:12:16 2016
@@ -67,7 +67,14 @@ limitations under the License.
<item name="Get Involved" href="/helping.html"/>
</menu>
- <menu name="Pluto 2.0">
+ <menu name="Pluto 3.0">
+ <item name="Getting Started" href="/v30/getting-started.html"/>
+ <item name="Deploying Portlets" href="/v30/deploying.html"/>
+ <item name="Portlet API" href="/v30/portlet-api.html"/>
+ <item name="Release Notes" href="/v30/release-notes.html"/>
+ </menu>
+
+ <menu name="Pluto 2.0">
<item name="Getting Started" href="/v20/getting-started.html"/>
<item name="Deploying" href="/v20/deploying.html"/>
<item name="Embedding" href="/v20/embedding.html"/>
@@ -75,6 +82,7 @@ limitations under the License.
<item name="App Servers" href="/v20/app-servers.html"/>
<item name="Powered By Pluto" href="/v20/powered.html"/>
</menu>
+
<menu name="Pluto 1.1">
<item name="Getting Started" href="/v11/getting-started.html"/>
<item name="Deploying" href="/v11/deploying.html"/>
Modified: portals/site/pluto/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/index.xml?rev=1772163&r1=1772162&r2=1772163&view=diff
==============================================================================
--- portals/site/pluto/src/site/xdoc/index.xml (original)
+++ portals/site/pluto/src/site/xdoc/index.xml Thu Dec 1 09:12:16 2016
@@ -43,43 +43,69 @@ limitations under the License.
</div>
<p>
- Pluto is the Reference Implementation of the Java Portlet Specification.
- The current version (2.0) of this specification is known as <a href="http://jcp.org/en/jsr/detail?id=286">JSR-286</a>.
- The previous specification version, <a href='http://jcp.org/en/jsr/detail?id=168'>JSR-168</a>,
covers
- version 1.0 of the specification. Pluto implements and is fully compliant with both
the 1.0 and 2.0 specifications.
+ The Apache Pluto project hosts the Java Portlet Specification Reference Implementation
(RI) and Technology Compliance Kit (TCK).
+ The current version (3.0) of this specification is known as <a href="http://jcp.org/en/jsr/detail?id=362">JSR-362</a>.
+ The previous specification version, <a href='http://jcp.org/en/jsr/detail?id=286'>JSR-286</a>,
covers
+ version 2.0 of the specification.
+ The first version of the specification, <a href='http://jcp.org/en/jsr/detail?id=168'>JSR-168</a>,
established
+ version 1.0. Pluto implements and is fully compliant with all three of these specifications.
</p>
</section>
- <section name="Pluto is a Portlet Container">
+ <section name="Pluto implements a Portlet Container">
<p>
A portlet container provides a runtime environment for portlets
implemented according to the Portlet API. In this environment portlets
- can be instantiated, used and finally destroyed. The portlet container
- is not a stand-alone container like the servlet container; instead it is
+ can be instantiated, used and finally destroyed. The Pluto portlet container
+ does not work stand-alone like the servlet container; instead it is
implemented as a thin layer on top of the servlet container and reuses
- the functionality provided by the servlet container. Architecturely, it provides
an
+ servlet container functionality. From an architecture point of view,
+ the Pluto portlet contaienr provides an
interface between the portal and portlets.
</p>
<p>
- Pluto serves as the portlet container for many portals, including <a href="http://portals.apache.org/jetspeed-2/">Apache
Jetspeed</a>.
- To accommodate the aggregation and display of diverse content in a dynamic manner,
a portal such as Jetspeed
- must provide a framework that integrates the various pluggable parts into a
- consistent user interface for the portal user. The pluggable parts are called <i>portlets</i>.
The contract, or programming API,
- between these portlets and a portal is known as the Portlet API. Pluto is the implementation
of this contract or API.
- </p>
+ Pluto serves as the portlet container for many portals, including <a
+ href="http://portals.apache.org/jetspeed-2/">Apache Jetspeed</a>. To
+ accommodate the aggregation and display of diverse content in a dynamic
+ manner, a portal such as Jetspeed must provide a framework that
+ integrates the various pluggable parts into a consistent user interface
+ for the portal user. The pluggable parts are called <i>portlets</i>.
The
+ contract, or programming API, between these portlets and a portal is
+ known as the Portlet API. Pluto is the implementation of this contract
+ or API.
+ </p>
+ <p>
+ Portlets are designed to be independent applications, just as servlets
+ are. However, rather than producing a complete web page, portlets
+ produce markup fragments that are intended to be aggregated with the
+ output from other portlets to produce a complete portal page. Portlets
+ can be developed without knowledge of the other portlets that the portal
+ places on the resulting web page. They need only obey the syntactic and
+ semantic rules laid out by the portlet specification.
+ </p>
</section>
- <section name='Developing with Pluto'>
+ <section name='Pluto Provides a Light-Weight, In-Memory Portal'>
+ <p>
+ The Pluto portlet container fully implements the Portlet API
+ specification and offers developers a working example platform from
+ which they can test their portlets. However, it is cumbersome to execute
+ and test the portlet container without a driver such as a full running
+ portal. To aid in portlet development and testing, and to provide a
+ framework for testing the portlet container itself, Pluto provides a
+ simple portal component that fulfills the requirements set out by the
+ JSR 362 Portlet Specification 3.0 standard.
+ </p>
<p>
- Pluto fully implements the Portlet API specification and
- offers developers a working example platform from which they can test
- their portlets. However, it is cumbersome to execute and test the portlet
- container without a driver such as a full running portal. Pluto's simple
- portal component is built only on the portlet container's and the JSR
- 286's requirements.
+ The term "in-memory" means that the Pluto portal component does not provide
+ a mechanism for data persistence. For example, portlets may set portlet
+ preferences, but Pluto does not persist the preference data across a server
+ restart.
</p>
- <p>If you want to get started with rapid portlet development with Pluto, see
the documentation on <a href='v20/getting-started.html'>Developing with Pluto</a>
+ <p>If you want to get started with rapid portlet development with Pluto,
+ see the documentation on
+ <a href='v30/getting-started.html'>Developing with Pluto</a>
</p>
</section>
- <section name='Differences from Servlets'>
+ <section name='How Portlets Differ from Servlets'>
<p>
In contrast to servlets, portlets may not do things like sending
redirects or errors to browsers directly, forwarding requests or writing
|