Author: msnicklous
Date: Thu Dec  1 14:38:46 2016
New Revision: 1772215

URL: http://svn.apache.org/viewvc?rev=1772215&view=rev
Log:
Added pages for v3.0. Updated page content

Added:
    portals/site/pluto/src/site/xdoc/v30/
    portals/site/pluto/src/site/xdoc/v30/deploying.xml
    portals/site/pluto/src/site/xdoc/v30/getting-started.xml
    portals/site/pluto/src/site/xdoc/v30/portlet-api.xml
    portals/site/pluto/src/site/xdoc/v30/release-notes.xml
    portals/site/pluto/src/site/xdoc/v30/tck.xml
Modified:
    portals/site/pluto/src/site/fml/faq.fml
    portals/site/pluto/src/site/resources/css/site.css
    portals/site/pluto/src/site/site.xml
    portals/site/pluto/src/site/xdoc/index.xml
    portals/site/pluto/src/site/xdoc/mission.xml
    portals/site/pluto/src/site/xdoc/resources.xml
    portals/site/pluto/src/site/xdoc/status.xml

Modified: portals/site/pluto/src/site/fml/faq.fml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/fml/faq.fml?rev=1772215&r1=1772214&r2=1772215&view=diff
==============================================================================
--- portals/site/pluto/src/site/fml/faq.fml (original)
+++ portals/site/pluto/src/site/fml/faq.fml Thu Dec  1 14:38:46 2016
@@ -21,20 +21,35 @@ limitations under the License.
 <faqs title="Frequently Asked Questions">
   <part id="general">
     <faq id="version">
-      <question>Which version of Pluto should I use?</question>
+      <question>Which version of Pluto 3.0 should I use?</question>
+      <answer>
+        <p>
+          Development for version 3.0 is nearly complete, but we don't have an 
official
+          release available yet. We hope to have it available in December 2016.
+          If you want to get started now, please see the Pluto 3.0
+          <a href="./v30/getting-started.html">Getting Started</a> section for 
information on cloning 
+          the Pluto repository, building the portal, and learning from the 
version 3.0 sample portlets.
+        </p>
+        <p>
+          All Pluto 2.x and 1.x versions are no longer active and only 
maintained for bug fixes. 
+        </p>
+      </answer>
+    </faq>
+
+    <faq id="version2.0">
+      <question>Which version of Pluto 2.0 should I use?</question>
       <answer>
         <p>
           The latest release from the 2.0 series (2.0.3) is the current
           stable release. We recommend that you use this if you
-          are looking for a stable release. 2.0 implements the latest Java 
Portlet Specification and requires Java 5 minimally.
+          are looking for a stable release. 2.0 implements JSR 286 Java 
Portlet Specification 2.0 and requires Java 5 as minimum.
         </p>
-
         <p>
-            All Pluto 1.x versions are no longer active and only maintained 
for bug fixes.currently under development. 
+          All Pluto 1.x versions are no longer active and only maintained for 
bug fixes. 
         </p>
       </answer>
     </faq>
-
+    
     <faq id="10">
       <question>I've seen references to Pluto 1.0.x and 1.1x. What are 
versions 1.x used for?</question>
       <answer>
@@ -136,6 +151,10 @@ limitations under the License.
     <faq id="encoding">
         <question>How can I change the default encoding of the Pluto 
Portal</question>
         <answer>
+            <p>
+              This is currently not supported with Pluto 3.0. The character 
encoding for 
+              render requests is set to UTF-8.
+            </p>
             <p>As of Pluto 1.1.5 you can change the default encoding of the 
Pluto Portal by
                editing the Pluto Portlet Servlet's web.xml.  Add an init-param 
with
                the name of "charset" and set the value to the desired 
character set.</p>

Modified: portals/site/pluto/src/site/resources/css/site.css
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/resources/css/site.css?rev=1772215&r1=1772214&r2=1772215&view=diff
==============================================================================
--- portals/site/pluto/src/site/resources/css/site.css (original)
+++ portals/site/pluto/src/site/resources/css/site.css Thu Dec  1 14:38:46 2016
@@ -206,3 +206,11 @@ body {
     border-top-color: #2E6794;
 }
 
+/**
+ * inline monocode for use with span tag
+ */
+
+.monoCode {
+    font-family: monospace;
+}
+

Modified: portals/site/pluto/src/site/site.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/site.xml?rev=1772215&r1=1772214&r2=1772215&view=diff
==============================================================================
--- portals/site/pluto/src/site/site.xml (original)
+++ portals/site/pluto/src/site/site.xml Thu Dec  1 14:38:46 2016
@@ -33,7 +33,7 @@ limitations under the License.
   <skin>  
     <groupId>org.apache.portals.pluto</groupId>
     <artifactId>pluto-site-skin</artifactId>
-    <version>2.1.0-SNAPSHOT</version>
+    <version>3.0-SNAPSHOT</version>
   </skin> 
   
   <body>
@@ -70,7 +70,8 @@ limitations under the License.
        <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="Portlet API 3.0" href="/v30/portlet-api.html"/>
+      <item name="Using the TCK" href="/v30/tck.html"/>
       <item name="Release Notes" href="/v30/release-notes.html"/>
        </menu>    
        

Modified: portals/site/pluto/src/site/xdoc/index.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/index.xml?rev=1772215&r1=1772214&r2=1772215&view=diff
==============================================================================
--- portals/site/pluto/src/site/xdoc/index.xml (original)
+++ portals/site/pluto/src/site/xdoc/index.xml Thu Dec  1 14:38:46 2016
@@ -59,8 +59,7 @@ limitations under the License.
         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
         servlet container functionality. From an architecture point of view, 
-        the Pluto portlet contaienr provides an
-        interface between the portal and portlets.
+        the Pluto portlet container provides an interface between the portal 
and portlets.
       </p>
       <p>
         Pluto serves as the portlet container for many portals, including <a
@@ -86,7 +85,7 @@ limitations under the License.
     <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
+        specification and offers developers a working example platform on
         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
@@ -114,7 +113,7 @@ limitations under the License.
         to servlets is that portlets rely on portal specific infrastructure
         functions such as access to user profile information, standard 
interface
         for storing/retrieving persistent settings, getting client information,
-        etc. Generally, portlets are administrated more dynamically than
+        etc. Also, portlets are generally administrated more dynamically than
         servlets.
       </p>
        </section>

Modified: portals/site/pluto/src/site/xdoc/mission.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/mission.xml?rev=1772215&r1=1772214&r2=1772215&view=diff
==============================================================================
--- portals/site/pluto/src/site/xdoc/mission.xml (original)
+++ portals/site/pluto/src/site/xdoc/mission.xml Thu Dec  1 14:38:46 2016
@@ -32,9 +32,7 @@ limitations under the License.
         a reference for interpretation of the specification, portlet developers
         a container with which compliant portlets can be tested, and portal
         developers a compliant container with which they can integrate.
-      </p>
-      <p>
-        The following document attempts to clarify the development priorities 
+        This following document attempts to clarify the development priorities 
         of the Apache Pluto project.
       </p>
       <p>

Modified: portals/site/pluto/src/site/xdoc/resources.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/resources.xml?rev=1772215&r1=1772214&r2=1772215&view=diff
==============================================================================
--- portals/site/pluto/src/site/xdoc/resources.xml (original)
+++ portals/site/pluto/src/site/xdoc/resources.xml Thu Dec  1 14:38:46 2016
@@ -29,8 +29,9 @@ limitations under the License.
     <section name="The Java Portlet Specifications">
       <p>
         <ul>
-          <li><a href="http://jcp.org/en/jsr/detail?id=168";>JSR-168: Portlet 
Specification 1.0</a></li>
-          <li><a href="http://jcp.org/en/jsr/detail?id=286";>JSR-286: Portlet 
Specification 2.0</a></li>
+          <li><a href="http://jcp.org/en/jsr/detail?id=362";>JSR 362: Portlet 
Specification 3.0</a></li>
+          <li><a href="http://jcp.org/en/jsr/detail?id=286";>JSR 286: Portlet 
Specification 2.0</a></li>
+          <li><a href="http://jcp.org/en/jsr/detail?id=168";>JSR 168: Portlet 
Specification 1.0</a></li>
         </ul>
       </p>
          </section>
@@ -53,6 +54,10 @@ limitations under the License.
       <p>
         <ul>
           <li>
+            <a 
href="https://static.rainfocus.com/oracle/oow16/sess/1462801563632001pOv8/ppt/JSR362-JavaOne-2016a.pdf";>Portlet
 Specification 3.0 Is Here!</a>
+            JavaOne presentation by Martin Scott Nicklous, September 2016
+          </li>
+          <li>
             <a 
href="http://www.developer.com/java/web/article.php/3547186";>Introduction to 
the Portlet Specification</a>
             by David H. DeWolf, September 2005
           </li>

Modified: portals/site/pluto/src/site/xdoc/status.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/status.xml?rev=1772215&r1=1772214&r2=1772215&view=diff
==============================================================================
--- portals/site/pluto/src/site/xdoc/status.xml (original)
+++ portals/site/pluto/src/site/xdoc/status.xml Thu Dec  1 14:38:46 2016
@@ -27,42 +27,63 @@ limitations under the License.
   <body>
     
 <section name="Project Status">
-      <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>
-      <subsection name="Pluto 2.0">
-        <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>
-     </subsection>
-        
-      <subsection name="Pluto 1.1">
-        <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>
-      </subsection>
-      <subsection name="Pluto 1.0.1">
-        <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>
-      </subsection>
-    </section>
+  <p>
+    Apache Pluto is a subproject of the Apache Portals Project. The current
+    stable release of Apache Pluto is version 2.0.3.
+    However, version 3.0 is under development and is nearly complete.
+    Pluto 3.0 provides the reference implementation and technology compliance 
kit for JSR 362 Portlet Spcification 3.0. 
+    It complies to the JSR 362 and JSR 286 standards.
+  </p>
+
+  <subsection name="Pluto 3.0">
+    <p>
+       Pluto 3.0 is the current main development branch. 
+       The Pluto 3.0 portlet container is the reference implementation
+       for JSR 362 Java Portlet Specification 3.0.
+       Pluto 3.0 drops the requirement for pre-processing portlet web 
applications. 
+       The JSR 362 specification adds configuration through annotation, 
asynchronous support
+       similar to the servlet asynchronous support, multipart form support, 
support for
+       CDI beans, method annotation support allowing portlet methods to reside 
in different classes,
+       and a JavaScript API that allows portal pages to function as 
single-page applications.
+       The Pluto 3.0 portlet container implements all JSR 362 features and 
passes the
+       TCK.
+       While doing so, Pluto 3.0 remains fully compliant to the 2.0 Portlet 
Specification,
+       meaning that version 2.0 portlets can run on the version 3.0 portlet 
container.
+    </p>
+  </subsection>
+  
+  <subsection name="Pluto 2.0">
+    <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>
+  </subsection>
     
-  </body>
+  <subsection name="Pluto 1.1">
+    <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>
+  </subsection>
   
+  <subsection name="Pluto 1.0.1">
+    <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>
+  </subsection>
+
+</section>
+</body>
 </document>
 
     
\ No newline at end of file

Added: portals/site/pluto/src/site/xdoc/v30/deploying.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/v30/deploying.xml?rev=1772215&view=auto
==============================================================================
--- portals/site/pluto/src/site/xdoc/v30/deploying.xml (added)
+++ portals/site/pluto/src/site/xdoc/v30/deploying.xml Thu Dec  1 14:38:46 2016
@@ -0,0 +1,126 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed  under the  License is distributed on an "AS IS" BASIS,
+WITHOUT  WARRANTIES OR CONDITIONS  OF ANY KIND, either  express  or
+implied.
+
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<document>
+  
+  <properties>
+    <title>Deploying a Portlet to Pluto Portal Version 3.0</title>
+  </properties>
+  
+  <body>
+    
+    <section name="Deploying a Portlet to Pluto Portal Version 3.0">
+      
+      <p>
+        The portlet war file is built just like any other web application war
+        file. No special processing steps are necessary. Note in particular 
that
+        the assembly processing step required by Pluto version 2.0 is no 
longer needed.
+      </p>
+      
+        <subsection name="Portlet Deployment">
+           <p>
+               To deploy a portlet application, simply deploy the application 
war
+               using any standard mechanism for your application server.  
There are many
+               maven plugins and ant tasks that can assist with this, or you 
can use
+               an administrative web console. This console is the Tomcat 
manager webapp in the
+               Pluto bundled distribution and is accessed via the 'Upload and 
deploy portlet war' link
+               on the page administration portlet. See the Help link on that 
portlet for more details.
+           </p>
+           <p>
+                  In the bundled distribution that uses Tomcat, deployment of 
an assembled war can simply
+                  be done by dropping the war into the webapps directory. You 
can automatically achive this
+                  by adding the following code within the plugins section of 
your maven pom.xml:
+           </p>
+          <source><![CDATA[
+       <plugin>
+        <artifactId>maven-antrun-plugin</artifactId>
+        <executions>
+          <execution>
+            <phase>integration-test</phase>
+            <configuration>
+              <tasks>
+                  <property environment="env"/>
+                   <!-- This assumes that you have set a CATALINA_HOME 
environmental variable -->
+                  <property name="pluto.home" value="${env.CATALINA_HOME}"/>
+                  <copy file="target/${pom.name}.war" 
todir="${pluto.home}/webapps"/>
+              </tasks>
+            </configuration>
+            <goals>
+              <goal>run</goal>
+            </goals>
+          </execution>
+        </executions>
+      </plugin>          
+          ]]></source>
+           <p>
+              Once the pom.xml file has been updated with this plugin, you can 
run the full build
+              and deployment using the command: mvn integration-test. The code 
assumes that you have set
+              the environmental variable CATALINA_HOME to the Pluto home 
directory. If that has not been
+              done, just set pluto.home from the command line with the -D 
flag. The command line would
+              then be: mvn -Dpluto.home=C:/pluto integration-test.
+           </p>
+           
+        </subsection>
+            
+      <subsection name="Portlet Publishing">
+        <p>
+        As soon as the portlet application (war) is deployed to the servlet 
container
+        the portlet application will be available to the portal and can be 
added to
+        pages using the page administration portlet. See the help mode in this 
portlet
+        for details on its use.
+        </p>
+        
+        <p><b>Portal Page Configuration</b></p>
+        <p>
+          If you'd like for your page configuration to be consistent throughout
+          restarts of the application server (currently placements made through
+          the page administration portlet is not persistent), you should then 
configure the page
+          layout in the portal-driver configuration file 
(pluto-portal-driver-config.xml).
+        </p>
+        <p>
+          The page can then be configured by adding a <code>page</code> child 
element of the <code>render-config</code> 
+          element, like this:
+          <source><![CDATA[
+<render-config default="Test Page">
+  ... ...
+  <page name="Your Portal Page Name"  
uri="/WEB-INF/themes/pluto-default-theme.jsp">
+    <portlet context="/your_portlet_app_context_path"
+             name="your_portlet_1"/>
+    <portlet context="/your_portlet_app_context_path"
+             name="your_portlet_2"/>
+  </page>
+</render-config>
+          ]]></source>
+        </p>
+        <p>
+          The <code>uri</code> attribute defines the theme of your portal page.
+          If you use <code>/WEB-INF/themes/pluto-default-theme.jsp</code> 
(which is the
+          default theme of Pluto Testsuite portlet app), your portlets will be
+          displayed in two columns. You can clone this file to customize your 
layout.
+          If you do so, make sure the <code>uri</code> attribute points to the 
new file.
+        </p>
+      </subsection>
+      
+    </section>
+    
+  </body>
+  
+</document>
+

Added: portals/site/pluto/src/site/xdoc/v30/getting-started.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/v30/getting-started.xml?rev=1772215&view=auto
==============================================================================
--- portals/site/pluto/src/site/xdoc/v30/getting-started.xml (added)
+++ portals/site/pluto/src/site/xdoc/v30/getting-started.xml Thu Dec  1 
14:38:46 2016
@@ -0,0 +1,208 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed  under the  License is distributed on an "AS IS" BASIS,
+WITHOUT  WARRANTIES OR CONDITIONS  OF ANY KIND, either  express  or
+implied.
+
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<document>
+  
+  <properties>
+    <title>Getting Started With Pluto 3.0</title>
+  </properties>
+  
+  <body>
+
+    <section name="Installing the Pluto 3.0 Binary Build">
+      
+      <div class="highlightBox">
+        <h4>About Pluto Distributions</h4>
+        <p>
+          You can download a pre-built Pluto bundle, or you can build Pluto 
from
+          the source code.
+          <ul>
+            <li>
+               <strong>pluto-bundle</strong> - Provides Pluto and Tomcat 
bundled together.
+               This is currently work in progress and not yet available
+            </li>
+            <li><strong>pluto-source-release</strong> - Provides the Pluto 
source code; requires
+                that you build and deploy Pluto on your own.</li>
+          </ul>
+        </p>
+      </div>
+      
+      <p>
+        <strong>Note: not yet ready!!</strong>
+      </p>
+      
+      <ol>
+        <li>
+          
+          Download the Pluto 3.0 binary distribution named 
<strong>pluto-current-bundle</strong> from 
+          a <a 
href="http://www.apache.org/dyn/closer.cgi/portals/pluto/";>distribution 
site</a>.</li>
+        <li>Unzip the binary distribution into a directory.</li>
+           <ol>
+              <li>pluto-&lt;version&gt; (pluto-3.0) will be the top level 
directory.</li>
+           </ol>   
+        <li>
+          Execute startup.bat (Windows) or startup.sh (Unix)
+          in pluto-&lt;version&gt;/bin.</li>
+        <li>
+          Use shutdown.bat/shutdown.sh to stop the portal
+        </li>
+        <li>
+          Browse to <a 
href="http://localhost:8080/pluto/portal";>http://localhost:8080/pluto/portal</a>
+        </li>
+        <li>
+          Login as user pluto (password=pluto) or tomcat (password=pluto).
+        </li>
+      </ol>
+
+    </section>
+       
+    <section name="Building Pluto 3.0 from Source">
+      
+      <p>
+        Pluto uses Maven 3 as its project management and build system. 
+        Pluto currently provides Maven plugins and ant scripts which can be 
used to
+        install the Pluto Portal.
+      </p>
+
+      <p>
+        The Pluto project uses the
+        <a href="https://git-scm.com/";>Git</a> version control
+        system.  If you're new to Git, you can find many books and online
+        resources to help you.
+      </p>
+
+       <h4>Software Prerequisites</h4>
+       
+       <p>
+         In order to build Pluto, you will need to have the following software 
+         packages installed on your system. For help in obtaining and 
installing
+         the packages, please access the appropriate web resources.
+         <ul>
+           <li>
+             A Java runtime environment, version 1.7.0 or later. See
+             <a href="https://java.com/en/download/";>the Java download site</a>
+           </li>
+           <li>
+             Apache Ant, version 1.9.3 or later. See
+             <a href="https://ant.apache.org/bindownload.cgi";>the Apache Ant 
download site</a>
+           </li>
+           <li>
+             Apache Maven, version 3.3.1 or later. See
+             <a href="https://maven.apache.org/download.cgi";>the Apache Maven 
download site</a>
+           </li>
+           <li>
+             Git version control software, version 2.0.0 or later. See
+             <a href="https://git-scm.com/downloads";>the Git download site</a>
+           </li>
+         </ul>
+         Note that your computer will also require access to the Internet 
during
+         the build process in order to access maven repositories and other 
information.
+       </p>
+
+      <h4>Obtaining Pluto 3.0 Source Code"</h4>
+       
+      <p>
+        To browse the Pluto source code online, access 
+        <a href="https://github.com/apache/portals-pluto";>the Apache Pluto 
Github mirror.</a>
+        This is current at all times.
+      </p>
+
+      <h4>Cloning the Pluto Repository</h4>
+      <p>
+        Anyone can clone the Pluto repository from the Github mirror.  
However, 
+        in order to update the repository, you will need to be an Apache pluto 
committer.
+        To clone the repository, switch to the directory in which you would 
like the 
+        code to reside, and execute the following command:
+      </p>
+      <p>
+        <code>git clone https://github.com/apache/portals-pluto.git 
pluto</code>
+      </p>
+      <p>
+        You now have the complete Pluto source code in the 
<code>./pluto</code> subdirectory. 
+      </p>
+
+      <h4>Building Pluto using Apache Ant</h4>
+      <p>
+        This is the easiest way to build Pluto. The Ant build script will use 
first 
+        build the binaries from source, then download and unpack the 
appropriate 
+        Apache Tomcat web container for the code version being built. It will 
then 
+        install pluto on Tomcat, adjusting the Tomcat configuration as 
necessary.
+      </p>
+      <p>
+        The <code>dist-build.xml</code> build script allows a number
+        of options for building and packaging the code. View the file for 
details.
+        The options used in the following command causes the demo portlets to 
be deployed
+        and retains the tomcat directory created during the build process 
rather
+        than deleting it. Execute the following command:
+      </p>
+      <p>
+        <code>ant -f dist-build.xml -DincludeDemos=true -DnoClean=true</code>
+      </p>
+      <p>
+        You now have Pluto built and deployed in the 
<code>./pluto/target/dist</code> subdirectory.
+        You can now switch to the 
<code>./pluto/target/dist/&lt;tomcat&gt;/bin</code> 
+        subdirectory and start Tomcat and Pluto as described in the next 
section.
+      </p>
+
+     <subsection name="Starting the Portal">
+       <p>
+         Now you are ready to use the Pluto Portal built from source. Start up 
tomcat by running
+         <code>startup.bat</code> (for windows) or <code>startup.sh</code> (for
+         *nix) in <code>&lt;TOMCAT_HOME&gt;/bin</code>, and browse to
+         <code>http://localhost:8080/pluto/portal</code>. Login to Pluto using
+         the user ID 'pluto' and password 'pluto'.
+       </p>
+     </subsection>
+   </section>
+
+   <section name="Using the Demo Portlets">
+     <p>
+       The Pluto distribution contains four version 3.0 portlet applications 
that
+       illustrate the use of all aspects of JSR 362 portlet programming.
+     </p>
+    <ul>
+      <li>
+        PortletHubDemo - Contains portlets that show how you can use the 
+        Portlet Hub JavaScript API to create portal-based single-page 
applications.
+      </li>
+      <li>
+        PortletV3AnnotatedDemo - Contains portlets that illustrate the use of 
+        the version 3.0 Extended Method Annotations feature.
+      </li>
+      <li>
+        PortletV3Demo - Contains portlets that illustrate miscellaneous aspects
+        of the API.
+      </li>
+      <li>
+        chatRoomDemo - Contains portlets that implement a simple chat room demo
+        based on the Portlet Hub JavaScript API and the portlet asynchronous
+        processing feature.
+      </li>
+    </ul>
+     <p>
+       The best way to view the source code would be to import the modules
+       mentioned above into your favorite IDE. 
+     </p>
+   </section>
+    
+</body>
+  
+</document>
+

Added: portals/site/pluto/src/site/xdoc/v30/portlet-api.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/v30/portlet-api.xml?rev=1772215&view=auto
==============================================================================
--- portals/site/pluto/src/site/xdoc/v30/portlet-api.xml (added)
+++ portals/site/pluto/src/site/xdoc/v30/portlet-api.xml Thu Dec  1 14:38:46 
2016
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed  under the  License is distributed on an "AS IS" BASIS,
+WITHOUT  WARRANTIES OR CONDITIONS  OF ANY KIND, either  express  or
+implied.
+
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<document>
+  
+  <properties>
+    <title>Portlet API version 3.0 Overview</title>
+  </properties>
+  
+  <body>
+
+  <section name="Portlet API version 3.0 Overview">
+    <p>
+      JSR 362 Portlet Specification 3.0 introduces many improvements to the
+      portlet programming model. It adds configuration through annotation,
+      asynchronous support similar to the servlet asynchronous support,
+      multipart form support, support for CDI beans, method annotation support
+      allowing portlet methods to reside in different classes, and a JavaScript
+      API that allows portal pages to function as single-page applications. The
+      Pluto 3.0 portlet container implements all JSR 362 features and passes 
the
+      TCK. While doing so, Pluto 3.0 remains fully compliant to the 2.0 Portlet
+      Specification, meaning that version 2.0 portlets can run on the version
+      3.0 portlet container.
+    </p>
+    <p>
+      To be continued ...
+    </p>
+  </section>
+    
+  </body>
+  
+</document>
+

Added: portals/site/pluto/src/site/xdoc/v30/release-notes.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/v30/release-notes.xml?rev=1772215&view=auto
==============================================================================
--- portals/site/pluto/src/site/xdoc/v30/release-notes.xml (added)
+++ portals/site/pluto/src/site/xdoc/v30/release-notes.xml Thu Dec  1 14:38:46 
2016
@@ -0,0 +1,43 @@
+<?xml version="1.0"?>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+    
+    http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<document>
+    <properties>
+        <title>Pluto Release Notes</title>
+        <subtitle>Pluto Release Notes</subtitle>
+    </properties>
+    <body>
+        <section name="Release Notes - Pluto 3.0">  
+            <p>
+              Pluto version 3.0 is a completely new release dedicated to the
+              implementation of JSR 362 Portlet Specification 3.0.
+            </p>
+            <p>
+            </p>
+        <subsection name="Bug">
+        <ul>
+        <li>
+        </li>
+        </ul>
+        </subsection>
+
+        <subsection name="Improvement">
+        </subsection>
+            
+        </section>
+    </body>
+</document>
\ No newline at end of file

Added: portals/site/pluto/src/site/xdoc/v30/tck.xml
URL: 
http://svn.apache.org/viewvc/portals/site/pluto/src/site/xdoc/v30/tck.xml?rev=1772215&view=auto
==============================================================================
--- portals/site/pluto/src/site/xdoc/v30/tck.xml (added)
+++ portals/site/pluto/src/site/xdoc/v30/tck.xml Thu Dec  1 14:38:46 2016
@@ -0,0 +1,112 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed  under the  License is distributed on an "AS IS" BASIS,
+WITHOUT  WARRANTIES OR CONDITIONS  OF ANY KIND, either  express  or
+implied.
+
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<document>
+  
+  <properties>
+    <title>Using the JSR 362 TCK</title>
+  </properties>
+  
+  <body>
+
+  <section name="Using the JSR 362 TCK">
+    <p>
+      The JSR 362 Technology Compliance Kit (TCK) is intended to be used by 
portal
+      vendors wishing to achieve JSR 362 compatibility for their product.
+      If you do not meet this description, you do not need to read this 
section.
+    </p>
+
+    <subsection name="Overview">
+      <p>
+      The TCK contains portlets and a test driver that are used to perform the
+      compatibility test. The portlets contain the code that actually 
exercises the
+      portlet API. The driver uses Selenium 2 driven by Junit to access the 
system
+      under test through a selenium webdriver browser.
+      </p><p>
+      You can click through the tests on the portal pages displayed by the 
system under
+      test, or you can use the test driver to automatically click through the 
tests
+      and collect the results. Since there are many test cases (>6000), you 
will 
+      generally use the test driver.
+      </p><p>
+      A test portlet may define multiple test cases. The test case names must 
be 
+      unique in the system, and must be of a form that can be used as portlet 
names 
+      and as Java Properties file keys.
+      </p><p>
+      Each portlet test module defines its own test case list and page file 
containing
+      the page definitions expected by the tests contained in the module.  
+      </p><p>
+      The build process generates a consolidated test case list and 
consolidated page 
+      file containing all test cases and page definitions for all test 
modules. The 
+      consolidated test case list maps the test case to the name of the page 
on which 
+      the test case is located.
+      </p><p>
+      The test driver works by reading the consolidated test case list. For 
each test
+      case, the driver accesses the specified page. It logs in if necessary, 
clicks
+      any available test case link, and collects the test case results from the
+      browser window.
+      </p><p>
+      The test driver accesses a TCK page by looking for and clicking a link 
whose
+      link text is equal to the page name. If the test driver cannot find the 
link on 
+      current page, it will access the test server login URL configured in the
+      portlet-tck_3.0/POM.xml file.
+      </p><p>
+      The test driver checks whether a login is necessary by checking for the
+      existence of an entry field that has the HTML element ID for the user 
name
+      field. If the user name field is available, the driver enters the user 
name and
+      password into the corresponding entry fields and submits the form. The 
username
+      HTML element ID, password element ID, username and password are 
configurable
+      in the portlet-tck_3.0/POM.xml file.
+      </p><p>
+      The driver checks for links to be clicked and results to be collected by
+      checking for specific HTML element IDs on the page. The HTML element IDs 
are
+      based on the test case name. From the point of view of the test driver 
there can
+      be several relevant element IDs on the page for each test case:
+      </p>
+      <ul>
+      <li>
+      "&lt;testcasename&gt;-setup"        - Test setup link      
+      </li><li>
+      "&lt;testcasename&gt;-clickme"      - Test execution link
+      </li><li>
+      "&lt;testcasename&gt;-results"      - Test results field; "Succeeded" or 
"Failed"
+      </li><li>
+      "&lt;testcasename&gt;-details"      - Test details field; provides 
failure reason
+      </li>
+      </ul>
+      <p>
+      After accessing the page on which the test case is to be found, the test 
driver
+      first looks for a setup link. If found, it clicks the link and waits for 
the
+      page to load.
+      </p><p>
+      The driver then looks for a test execution link. If found, 
+      it clicks the link, waits for the new page to load, and then checks for 
the
+      result elements.
+      </p><p>
+      The driver reads the contents of the HTML elements that have the results 
and
+      details element IDs and analyzes the results string to determine test 
case
+      success or failure.
+      </p>
+    </subsection>
+  </section>
+    
+  </body>
+  
+</document>
+



Reply via email to