portals-pluto-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From e..@apache.org
Subject svn commit: r642585 [3/4] - in /portals/pluto/trunk: ./ maven-pluto-plugin/ maven-pluto-plugin/src/site/ maven-pluto-plugin/src/site/apt/ pluto-ant-tasks/src/site/ pluto-ant-tasks/src/site/apt/ pluto-container/ pluto-container/src/site/ pluto-container...
Date Sat, 29 Mar 2008 19:05:26 GMT
Added: portals/pluto/trunk/src/site/xdoc/v101/install.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v101/install.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v101/install.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v101/install.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,277 @@
+<?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 1.0.1</title>
+  </properties>
+  
+  <body>
+    
+    <section name="Installation Guide">
+      <p>
+        This install guide covers the following types of installations:
+        <ul>
+          <li><a href="#Installing_Pluto_Distributions">Installing Pluto Distributions</a></li>
+          <li><a href="#Installing_Portlets">Installing Portlets</a></li>
+          <ul>
+            <li><a href="#Installing_With_Maven">Installing with Maven</a></li>
+            <li><a href="#Using_the_Admin_Portlet_Application">Using the Admin Portlet Application</a></li>
+          </ul>
+        </ul>
+      </p>
+    </section>
+    
+    <section name="Installing Pluto Distributions">
+      
+      <subsection name="Binary Distribution">
+        <p>
+          The binary distribution of Pluto is packaged with Tomcat (currently
+          version 5.5.9).  Pluto leverages Tomcat to provide the web container
+          in which the Pluto portlet container executes. The binary distribution
+          includes the Pluto Portlet Container, The Portal Driver, the Pluto
+          Testsuite and the Admin Portlet application.
+        </p>
+        <p>
+          To install the binary distribution:
+          <ul>
+            <li><a href="mirrors.cgi">Download</a> the current binary
+            distribution of Pluto</li>
+            <li>Extract the binary distribution to a directory from here forward
+            refered to as <code>"&lt;PLUTO_HOME&gt;"</code>.</li>
+            <li>Startup the server by using the appropriate tomcat startup
+            script located at <code>&lt;PLUTO_HOME&gt;/bin</code>.
+            For *nix use <code>startup.sh</code>; for windows use
+            <code>startup.bat</code>.</li>
+            <li>By default Tomcat 5.5 uses JDK 1.5 (J2SE 5.0). In order to run
+            it with JDK 1.4, a compatibility package needs to be downloaded and
+            installed. See the Running.txt file in the root directory for
+            details.</li>
+            <li>Point your browser to <code>http://localhost:8080/pluto/portal</code>,
+            the Pluto Driver, and your ready to go!</li>
+          </ul>
+        </p>
+      </subsection>
+      
+      <subsection name="Library Distributions">
+        <p>
+          The pluto library distributions are packaged to allow integration with
+          an external portal server.
+        </p>
+        <p>
+          To install the library distributions to your portal server, ensure
+          that the pluto-x.x.x.jar is loaded by a classloader to which both the
+          portal and portlet application web apps have access.
+        </p>
+      </subsection>
+      
+      <subsection name="Source Distribution">
+        <p>
+          Installing the source distribution requires the most effort, and is
+          recomended only for those individuals who are interested in modifying
+          the container.  The source distribution is basically a snapshot of the
+          source code repository at a given time. Because of this, please see
+          the build instructions, which will provide information about how to
+          build Pluto from scratch.
+        </p>
+        <p>
+          To install the source distribution into Tomcat:
+          <ul>
+            <li>Install Java 1.4 or greater</li>
+            <li>Install Maven 1.0 or greater</li>
+            <li>Install Tomcat 4.x or Tomcat 5.x to a directory from here
+            forward refered to as <code>&lt;TOMCAT_HOME&gt;</code></li>
+            <li>Edit your <code>&lt;PLUTO_HOME&gt;/build.properties</code> to
+            include the following properties:
+              <table>
+                <tr>
+                  <th>Property</th>
+                  <th>Value</th>
+                  <th>Example(s)</th>
+                </tr>
+                <tr>
+                  <td>maven.tomcat.home</td>
+                  <td>Tomcat Installation Directory</td>
+                  <td><code>/usr/local/apache-tomcat.5.0.27</code>,
+                      <code>c:\\apache-tomcat.5.0.27</code></td>
+                </tr>
+                <tr>
+                  <td>maven.tomcat.version.major</td>
+                  <td>Tomcat Major Version Number</td>
+                  <td>5</td>
+                </tr>
+              </table>
+            </li>
+            <li>From <code>&lt;PLUTO_HOME&gt;</code> issue the command:
+            <code>maven fullDeployment</code></li>
+            <li>Startup the server by using the appropriate Tomcat startup
+            script located at <code>&lt;PLUTO_HOME&gt;/bin</code>.
+            For *nix use <code>startup.sh</code>; for windows use
+            <code>startup.bat</code>.</li>
+            <li>Point your browser to
+            <code>http://localhost:8080/pluto/portal</code>, the Pluto Driver,
+            and your ready to go!</li>
+          </ul>
+        </p>
+      </subsection>
+      
+    </section>
+    
+    <section name="Installing Portlets">
+      
+      <subsection name="Installing with Maven">
+        <p>
+          <span style="color: #FF0000;">Currently, to automate the
+          deployment/installation of portlets you must utilize the source
+          distribution of pluto. Alternatively, you could use the
+          <a href="#Using_the_Admin_Portlet_Application">Admin Portlet
+          Application</a> to install custom portlets.</span>
+        </p>
+        <p>
+          In order to deploy a portlet application to pluto, you must follow the
+          steps below:
+        </p>
+        <p>
+          <b>Step 1:</b> Assemble your portlet application into a valid war.
+        </p>
+        <p>
+          <b>Step 2:</b> Run the maven deploy goal on your war. This can be done
+          by running this command line in the deploy subdirectory:
+          <source><![CDATA[
+maven deploy -Ddeploy=/MyPathToMyPortlet/target/MyPortlet.war
+          ]]></source>
+          See the <a href="developer/build_source.html">Building From Source</a>
+          document for detailed instructions.
+        </p>
+        <p>
+          Alternatively, there is an interactive ant script in the
+          <code>portlet-deploy</code> directory that will perform the same task
+          as the Maven deployment goal.
+        </p>
+        <p>
+          <b>Step 3:</b> Modify the Portlet Entity Registry and the Page
+          Registry and Portlet Contexts files. These configuration files are
+          located at:
+          <ul>
+            <li><code>[portal-home]/WEB-INF/data/portletentityregistry.xml</code></li>
+            <li><code>[portal-home]/WEB-INF/data/pageregistry.xml</code></li>
+            <li><code>[portal-home]/WEB-INF/data/portletcontexts.txt</code></li>
+          </ul>
+        </p>
+        <p>
+          The Portlet Entity Registry file requires that you specify an
+          application and a Portlet ID for your new Portlet. The Application ID
+          must be unique. It also needs to know the name of the Portlet so that
+          it can go out and find it in the webapps path. Furthermore, this
+          information is used to map the Portlet name to the appropriate class
+          path for loading the class. The following is an example of some
+          additions you can make to the entity registry file:
+        </p>
+        <p>
+          <source><![CDATA[
+<application id="6">
+  <definition-id>MyPortlet</definition-id>
+  <portlet id="1">
+    <definition-id>MyPortlet.MyPortlet</definition-id>
+  </portlet>
+</application>
+          ]]></source>
+        </p>
+        <p>
+          The Page Registry provides Pluto with the layout information for your
+          Portlet. The names used in the fragments must be unique as done in
+          the following example:
+        </p>
+        <p>
+          <source><![CDATA[
+<fragment name="MyPortlet" type="page">
+  <navigation>
+    <title>My First Portlet</title>
+    <description>...</description>
+  </navigation>
+  
+  <fragment name="row3" type="row">
+    <fragment name="col3" type="column">
+      <fragment name="p4" type="portlet">
+        <property name="portlet" value="6.1"/>
+      </fragment>
+    </fragment>
+  </fragment>
+  
+  ... ...
+
+</fragment>
+          ]]></source>
+        </p>
+        <p>
+          The Portlet Contexts file (<code>portletcontexts.txt</code>) lists
+          the webapp contexts for each portlet application that runs in Pluto.
+          Each portlet app has a line in this file corresponding to a path and
+          starting with a slash ('/'). In Tomcat, this path is the value of the
+          'path' attribute of the 'Context' element in a context XML descriptor
+          in <code>&lt;TOMCAT_HOME&gt;/conf/Catalina/localhost</code>
+          (or another 'conf' subdirectory).
+        </p>
+      </subsection>
+      
+      <subsection name="Using the Admin Portlet Application">
+        <p>
+          The Admin Portlet Application allows you to deploy custom portlets
+          using an interface in Pluto's portal. This application automatically
+          places the custom portlets to their proper place and updates the
+          registries.
+        </p>
+        <p>
+          Deploying a custom portlet application to Pluto using the Admin
+          Portlet Application requires the following steps:
+          <ul>
+            <li>Assemble your portlet application into a valid war.</li>
+            <li>Start Pluto and navigate to
+            <code>http://localhost:8080/pluto/portal</code>, the local Pluto
+            home page.</li>
+            <li>Click on the Admin navigation link. The Admin Portlet App should
+            appear.</li>
+            <li>In the Deploy War Portlet, click on the Browse button and select
+            your war file</li>
+            <li>Click on the Submit button of the Deploy War Portlet</li>
+            <li>In the resulting page, fill in the Title, Description (optional),
+            and the number of rows and columns you desire for laying out the
+            portlets. Click on Submit</li>
+            <li>In the resulting page, select from the drop downs which portlet
+            will be deployed in a particular row and column. Click on Submit.</li>
+            <li>After returning to the Deploy War Portlet 'home page', click on
+            the blue 'Hot deploy ...' link to hot deploy the new portlet app and
+            get redirected to its page.</li>
+          </ul>
+        </p>
+        <p>
+          Check out the Deploy War Portlet's help mode (help link) for
+          information on redeploying and undeploying portlets and
+          troubleshooting problems.
+        </p>
+      </subsection>
+      
+    </section>
+    
+  </body>
+  
+</document>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v101/install.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v101/install.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: portals/pluto/trunk/src/site/xdoc/v101/resources.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v101/resources.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v101/resources.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v101/resources.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,65 @@
+<?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>Pluto Project</title>
+  </properties>
+  
+  <body>
+    
+    <section name="Resources">
+      <p>
+        <table>
+          <tr>
+            <th>Resource</th>
+            <th>Type</th>
+          </tr>
+          <tr>
+            <td><a href="http://jcp.org/en/jsr/detail?id=168">JSR 168</a></td>
+            <td>JCP Request Info</td>
+          </tr>
+          <tr>
+            <td><a href="http://jcp.org/en/jsr/detail?id=286">JSR 286</a></td>
+            <td>JCP Request Info</td>
+          </tr>
+          <tr>
+            <td><a href="http://jcp.org/aboutJava/communityprocess/final/jsr168/index.html">Portlet Specification 1.0</a></td>
+            <td>Specification</td>
+          </tr>
+          <tr>
+            <td><a href="http://people.apache.org/~zheng/pluto/chinese/">Chinese translation of Pluto website</a></td>
+            <td>Documentation</td>
+          </tr>
+          <tr>
+            <td><a href="http://today.java.net/pub/a/today/2005/02/18/josso.html">Integrating Java Open Single Sign-On in Pluto</a></td>
+            <td>Documentation</td>
+          </tr>
+          <tr>
+            <td><a href="http://www.theserverside.com/articles/article.tss?l=ClusteringTomcat">Clustering JSR-168 Portlet Applications in Tomcat</a></td>
+            <td>Documentation</td>
+          </tr>
+        </table>
+      </p>
+    </section>
+    
+  </body>
+</document>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v101/resources.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v101/resources.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: portals/pluto/trunk/src/site/xdoc/v101/userguide/index.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v101/userguide/index.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v101/userguide/index.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v101/userguide/index.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,88 @@
+<?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 User Guide</title>
+</properties>
+
+<body>
+<section name="User Guide">
+<subsection name="Prerequisites">
+  <p>It is expected that the reader of the user guide documentation
+     should has an understanding of Java Web Application development, and 
+     Java Portlet Development.</p>
+</subsection>
+
+<subsection name="Pluto - The Pluto Container">
+<p>
+   Pluto is the reference implementation of the Portlet Specification.
+   It is a portlet container which manages the lifecycle and request
+   processing of portlets which adhere to the specification.
+</p>
+   
+<p>
+   In an of itself, Pluto is not very usefull to the end user.
+   As a container, it does not have any understanding of portlet
+   invocation, portlet aggregation or other portal specific features. 
+</p>
+
+<p>
+  For more information on how to integrate Pluto into your portal, 
+  please see the <A href="../developer/integration.html">developer guides</A>.
+</p>
+
+</subsection>
+
+<subsection name="Pluto Portal Driver - The Test Portal">
+<p>
+  The Pluto Portal Driver is a simple portal implementation that
+  is provided for convenience sake. It's purpose is to provide
+  aggregation support so that Pluto may be easily tested, and
+  portlets may be easily developed.
+</p>
+
+<p>
+  For information on how to use, configure, and customize the 
+  Portal Driver, please see the 
+  <A href="portal.html">Portal Driver User Guide</A>.
+</p>
+
+</subsection>
+
+<subsection name="Pluto TestSuite - The Test Portlet Application">
+<p>
+  The Pluto TestSuite is a Portlet Application which can be used to test
+  Portlet Implementations.  The TestSuite tests several basic portlet
+  functions and is a quick and dirty way to test for Portlet Specification
+  compliance.  While a quick test of a portal using the testsuite won't 
+  garuntee compliance, it will help flag any notable incompliance.
+</p>
+
+<p>
+  For information on how to use and configure the TestSuite, please see
+  the <A href="testsuite.html">TestSuite User Guide</A>
+</p>
+</subsection>
+
+</section>
+
+</body>
+</document>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v101/userguide/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v101/userguide/index.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: portals/pluto/trunk/src/site/xdoc/v101/userguide/portal.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v101/userguide/portal.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v101/userguide/portal.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v101/userguide/portal.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,446 @@
+<?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>User Guide: Pluto Portal Driver</title>
+</properties>
+
+<body>
+<section name="User Guide: Pluto 1.0.1 Portal Driver">
+  <p>
+  <ul>
+  <li><A href="#Limitations">Limitations</A></li>
+  <li><A href="#Configuration">Configuration</A></li>
+  <li><A href="#Defining_the_Portal_Layout">Defining the Portal Layout</A></li>
+  <li><A href="#Advanced_Customization">Advanced Customization</A></li>
+  <li><A href="#Internationalization">Internationalization</A></li>
+  <li><A href="#Further_Information">Further Information</A></li>
+  </ul>
+  </p>
+</section>
+
+
+<section name="Limitations">
+    <p>
+       The Pluto Portal is intended to provide an example implementation of
+       how to integrate Pluto into a portal. Additionally, it may be used for
+       the development of compliant portlets.  In some places it lacks the 
+       flexibility a true portal supplies. The portal is not designed for 
+       maximum performance, but rather simplicity.
+     </p>
+
+     <p>
+       To learn how to embed Pluto in your own portal, see the
+	   "<a href="../developer/integrate.html">Integration Guide</a>" document.</p>
+</section>
+
+<section name="Configuration">
+  <subsection name="Default Configuration">
+    <p>
+      Upon installation of the binary distribution of Pluto 1.0.1, the portal
+      driver is made available at <code>http://localhost:8080/pluto/portal</code>.
+      The default installation is configured with a portal page which
+      contains two instances of the testsuite portlet and an administration.
+      portlet for installing custom portlets and viewing the repositories.  
+      This configuration is also the default for installations completed from the source distribution
+      (or Subversion repository) and deployed using the Pluto deploy tool.
+    </p>
+    <p>
+      <table>
+      <caption><B>Default Configuration for Binary Distributions:</B></caption>
+      <tr><th>Configuration</th>
+          <th>Platform</th>
+          <th>Value</th><th>Description</th></tr>
+      <tr><td>Installation Directory</td>
+          <td>All</td>
+          <td>&lt;PLUTO_HOME&gt;</td>
+          <td>The directory to which you unarchived the distribution</td></tr>
+      <tr><td>Startup Scripts</td>
+          <td>*nix</td>
+          <td>&lt;PLUTO_HOME&gt;/bin/startup.sh</td>
+          <td>The script used to startup the portal driver</td></tr>
+      <tr><td>Startup Scripts</td>
+          <td>Windows</td>
+          <td>&lt;PLUTO_HOME&gt;/bin/startup.bat</td>
+          <td>The script used to startup the portal driver</td></tr>
+      <tr><td>Context Configuration</td>
+          <td>All</td>
+          <td>&lt;PLUTO_HOME&gt;/conf/Catalina/localhost/pluto.xml</td>
+          <td>The Tomcat Context Configuration file</td></tr>
+      </table>
+    </p>
+
+    <p>
+      <table>
+      <caption><B>Default Configuration for Source Distributions:</B></caption>
+      <tr><th>Configuration</th>
+          <th>Platform</th>
+          <th>Value</th><th>Description</th></tr>
+      <tr><td>Installation Directory</td>
+          <td>All</td>
+          <td>${maven.tomcat.home}</td>
+          <td>The tomcat installation directory to which pluto has been installed</td></tr>
+      <tr><td>Startup Scipts</td>
+          <td>*nix</td>
+          <td>${maven.tomcat.home}/bin/startup.sh</td>
+          <td>The script used to startup the portal driver</td></tr>
+      <tr><td>Startup Scipts</td>
+          <td>Windows</td>
+          <td>${maven.tomcat.home}/bin/startup.bat</td>
+          <td>The script used to startup the portal driver</td></tr>
+      <tr><td>Context Configuration</td>
+          <td>Tomcat 5.5</td>
+          <td>${maven.tomcat.home}/conf/Catalina/localhost/pluto.xml</td>
+          <td>The Tomcat Context Configuration file</td></tr>
+      </table>
+    </p>
+
+    <p>When the Pluto Portal is first installed, it is made available at 
+       the address http://localhost:8080/pluto/portal/.</p>
+
+				<p>This location can be customized, using standard Tomcat functionality. To modify the <i>pluto</i> part of the
+				location, alter the path mapping in pluto's context configuration file <i>pluto.xml</i></p>
+
+				<p>Under Tomcat 5.5, pluto.xml will be located
+				in the ${TOMCAT_HOME}/conf/Catalina/ directory. </p>
+
+				<p>In order to modify the context Pluto is running under, modify the <i>path</i> attribute:</p>
+				<p>
+				<b>Before:</b>
+				<source>
+	&lt;Context path="/pluto" docBase="pluto" crossContext="true"&gt;
+	&lt;/Context&gt;
+				</source>
+				</p>
+				<p><b>After:</b>
+				<source>
+	&lt;Context path="/newlocation" docBase="pluto" crossContext="true"&gt;
+	&lt;/Context&gt;
+				</source>
+				</p>
+				
+				<p>You might also need to modify host.name and portletcontainer.uniquename in 
+				${TOMCAT_HOME}/webapps/pluto/WEB-INF/config/services/ConfigService.properties.
+				</p>
+
+				<p>After this modification (and restarting Tomcat),
+				the Pluto Portal will be available at the address http://servername/newlocation/portal/.
+				Further information on customizing the context configuration is available for
+				<a href="http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/context.html">Tomcat 5.5</a>.
+				</p>
+
+				<p>To modify the <i>portal</i> part of the location, alter the <i>url-pattern</i> for the
+				<i>pluto</i> servlet. This mapping can be found in the <i>web.xml</i> configuration file
+				for the Pluto web application.</p>
+				<p>
+				<b>Before:</b>
+				<source>
+    &lt;servlet-mapping&gt;
+       &lt;servlet-name&gt;pluto&lt;/servlet-name&gt;
+       &lt;url-pattern&gt;/portal/*&lt;/url-pattern&gt;
+    &lt;/servlet-mapping&gt;
+				</source>
+				</p>
+				<p>
+				<b>After:</b>
+				<source>
+    &lt;servlet-mapping&gt;
+       &lt;servlet-name&gt;pluto&lt;/servlet-name&gt;
+       &lt;url-pattern&gt;/app/*&lt;/url-pattern&gt;
+    &lt;/servlet-mapping&gt;
+				</source>
+				</p>
+				
+				<p>You will also need to modify servlet.insecure in ${TOMCAT_HOME}/webapps/pluto/WEB-INF/config/services/ConfigService.properties.
+				</p>
+				
+				<p>After these modifications (and restarting Tomcat),
+				the Pluto Portal will be available at the address http://servername/newlocation/app/
+				(assuming that the previous modification was also applied).
+				</p>
+			</subsection>
+
+			<subsection name="Registering Portlets for use">
+				<p>In order to use a Portlet in the Pluto Portal it needs to be registered. The Pluto Portal
+				keeps page registrations in a file named <i>portletentityregistry.xml</i> in the directory
+				${TOMCAT_HOME}/webapps/pluto/data.</p>
+
+				<p>By default, this file looks like this:
+				<source>
+&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;portlet-entity-registry&gt;
+    &lt;application id="3"&gt;
+        &lt;definition-id&gt;testsuite&lt;/definition-id&gt;
+        &lt;portlet id="1"&gt;
+            &lt;definition-id&gt;testsuite.TestPortlet1&lt;/definition-id&gt;
+            &lt;preferences&gt;
+                &lt;pref-name&gt;TestName4&lt;/pref-name&gt;
+                &lt;pref-value&gt;TestValue4&lt;/pref-value&gt;
+                &lt;read-only&gt;true&lt;/read-only&gt;
+            &lt;/preferences&gt;
+        &lt;/portlet&gt;
+    &lt;/application&gt;
+    &lt;application id="4"&gt;
+        &lt;definition-id&gt;testsuite&lt;/definition-id&gt;
+        &lt;portlet id="1"&gt;
+            &lt;definition-id&gt;testsuite.TestPortlet2&lt;/definition-id&gt;
+            &lt;preferences&gt;
+                &lt;pref-name&gt;TestName4&lt;/pref-name&gt;
+                &lt;pref-value&gt;TestValue4&lt;/pref-value&gt;
+                &lt;read-only&gt;true&lt;/read-only&gt;
+            &lt;/preferences&gt;
+        &lt;/portlet&gt;
+    &lt;/application&gt;
+&lt;/portlet-entity-registry&gt;
+				</source>
+				</p>
+				<p>Each &lt;application&gt; tag defines one application (corresponding to one web-app on the
+				portal container), which can contain multiple &lt;portlet&gt; tags.
+				The "id" attribute in this tag identifies the application, and it does not need to be numeric.</p>
+
+				<p>The &lt;definition-id&gt; tag within the &lt;application&gt; refers to the name of the
+				web-app that contains the portlets in this application.</p>
+
+				<p>Each &lt;portlet&gt; tag defines one portlet. The "id"
+				attribute in this tag identifies the portlet. Note that the application id concatenated with the portlet
+				id will be mapped to the "value" attribute in the &lt;proprety&gt; tag in pageregistry.xml
+				(which is explained later).</p>
+
+				<p>Each &lt;preferences&gt; tag within the &lt;portlet&gt; tag defines name/value pairs for
+				the PorletPreferences.</p>
+
+				<p>In the example above two Portlet applications are made available to the portal with the
+				ids of "3" and "4". Both happen to point to the same webapp (<tt>&lt;definition-id&gt;testsuite&lt;/definition-id&gt;</tt>).
+				Both applications define a single Portlet each. Application id 3 uses the Portlet <i>TestPortlet1</i>
+				(<tt>&lt;definition-id&gt;testsuite.TestPortlet1&lt;/definition-id&gt;</tt>), while Application id 4 uses
+				the Portlet <i>TestPortlet2</i>	(<tt>&lt;definition-id&gt;testsuite.TestPortlet2&lt;/definition-id&gt;</tt>).
+				Note that prefixing the name of the Portlet with the name of web application (<i><b>testsuite</b>.TestPortlet1</i>)
+				is required.
+				</p>
+
+				<p>
+					Since Pluto 1.0.1-rc2, another configuration file, portletcontexts.txt, has been 
+				        included in the Pluto portal. The Portlet Contexts file ($PLUTO_HOME/WEB-INF/data/portletcontexts.txt) 
+				        lists the webapp 
+				        contexts for each portlet application that runs in Pluto. Each portlet app has a line in this 
+				        file corresponding to a path and starting with a slash ('/'). In Tomcat, this path is the value 
+				        of the 'path' attribute of the 'Context' element in a context XML descriptor in 
+				        $TOMCAT_HOME/conf/Catalina/localhost (or another 'conf' subdirectory).
+
+				</p>
+
+				<p>The Portlets themselves are defined in the portlet.xml configuration file within the
+				testsuite web application.	In that file there are two Portlets defined,
+				<i>TestPortlet1</i> and <i>TestPortlet2</i>, both of which point to the same
+				portlet class (<tt>org.apache.pluto.portalImpl.portlet.TestPortlet</tt>).
+				See the javax.portlet specification (JSR-168) for futher details on using the portlet.xml file.
+				</p>
+			</subsection>
+
+			<subsection name="Defining the Portal Layout">
+				<p>Once the Portlets available have been defined the Portal layout needs to be defined.	In the
+				Pluto Portal the file <i>pageregistry.xml</i> in the directory ${TOMCAT_HOME}/webapps/pluto/data defines this layout.</p>
+
+				<p>When Pluto is first installed, pageregistry.xml looks like this:
+			<source>
+&lt;?xml version="1.0"?&gt;
+&lt;portal&gt;
+    &lt;fragment name="navigation" class="org.apache.pluto.portalImpl.aggregation.navigation.TabNavigation"&gt;
+    &lt;/fragment&gt;
+
+    &lt;fragment name="test" type="page"&gt;
+        &lt;navigation&gt;
+            &lt;title&gt;Test&lt;/title&gt;
+            &lt;description&gt;...&lt;/description&gt;
+        &lt;/navigation&gt;
+
+        &lt;fragment name="row" type="row"&gt;
+            &lt;fragment name="col1" type="column"&gt;
+
+                &lt;fragment name="p1" type="portlet"&gt;
+                    &lt;property name="portlet" value="3.1"/&gt;
+                &lt;/fragment&gt;
+                &lt;fragment name="p2" type="portlet"&gt;
+                    &lt;property name="portlet" value="4.1"/&gt;
+                &lt;/fragment&gt;
+
+            &lt;/fragment&gt;
+        &lt;/fragment&gt;
+    &lt;/fragment&gt;
+&lt;/portal&gt;
+			</source>
+				</p>
+
+				<p>This configuration results in the Portal being displayed
+				(from the url http://servername/pluto/portal/test/) as Figure 1 shows.</p>
+
+				<div align="center">
+					<p>
+							<a href="../../images/v101/default_portal_layout.jpg">
+                <img src="../../images/v101/default_portal_layout.jpg"
+                     alt="Default Portal Layout" width="500"/></a>
+					</p>
+					<p>
+						<i><b><font size="-1">Figure 1. Default Portal Layout. Click on the picture to enlarge it</font></b></i>
+					</p>
+				</div>
+
+				<p>Working from the top of pageregistry.xml down, the first important section we come to is:
+				<source>
+&lt;fragment name="navigation" class="org.apache.pluto.portalImpl.aggregation.navigation.TabNavigation"&gt;
+&lt;/fragment&gt;
+				</source>
+				</p>
+				<p>This section tells the Portal to add a navigation menu to the user interface. Each fragment of
+				type <i>page</i> will be displayed in the navigation menu, provided the fragment has a &lt;navigation&gt;
+				sub-element. Removing the <tt>&lt;fragment name="navigation" ...&gt;&lt;/fragment&gt;</tt> section
+				will result in no navigation menu being displayed.
+				</p>
+
+				<p>
+				The next section is:
+				<source>
+    &lt;fragment name="test" type="page"&gt;
+        &lt;navigation&gt;
+            &lt;title&gt;Test&lt;/title&gt;
+            &lt;description&gt;...&lt;/description&gt;
+        &lt;/navigation&gt;
+		...
+		...
+    &lt;/fragment&gt;
+				</source>
+				</p>
+				<p>
+				This section defines a Portal "page", which is simply a container for one or more Portlets. The <i>name</i>
+				attribute must be unique within the pageregistry.xml file (if this constraint is not met an error
+				message <i>Fragment with this name &lt;duplicated name&gt; already exists in the pageregistry.xml.</i> will be written to your
+				log and your Pluto web application will fail to load).
+				</p>
+				<p>
+				The navigation subsection is used by the navigation menu (discussed previously). The &lt;title&gt;...&lt;/title&gt;
+				defines the label that will be shown in the navigation menu. The &lt;description&gt;...&lt;/description&gt;element
+				is not used.
+				</p>
+
+				<p>Inside the <tt>&lt;fragment type="page" .... &gt;&lt;/fragment&gt;</tt> elements we find
+				<source>
+    &lt;fragment name="row" type="row"&gt;
+        &lt;fragment name="col1" type="column"&gt;
+
+            &lt;fragment name="p1" type="portlet"&gt;
+                &lt;property name="portlet" value="3.1"/&gt;
+            &lt;/fragment&gt;
+            &lt;fragment name="p2" type="portlet"&gt;
+                &lt;property name="portlet" value="4.1"/&gt;
+            &lt;/fragment&gt;
+
+        &lt;/fragment&gt;
+    &lt;/fragment&gt;
+				</source>
+				</p>
+				<p>This defines the layout of the Portal "page". In this case two Portlets will be laid out in two columns,
+				nested inside a single row.
+				</p>
+				<p>The configuration below will give the page a layout of two rows, with a Portlet in each. Note that the names of all fragments
+				need to be unique.
+				<source>
+	&lt;fragment name="row1" type="row"&gt;
+	    &lt;fragment name="col1" type="column"&gt;
+	        &lt;fragment name="p1" type="portlet"&gt;
+	            &lt;property name="portlet" value="3.1"/&gt;
+	        &lt;/fragment&gt;
+	    &lt;/fragment&gt;
+	&lt;/fragment&gt;
+	&lt;fragment name="row2" type="row"&gt;
+	    &lt;fragment name="col2" type="column"&gt;
+	        &lt;fragment name="p2" type="portlet"&gt;
+	            &lt;property name="portlet" value="4.1"/&gt;
+	        &lt;/fragment&gt;
+	    &lt;/fragment&gt;
+	&lt;/fragment&gt;
+				</source>
+				</p>
+				<p>The section
+				<source>
+    &lt;fragment name="p1" type="portlet"&gt;
+        &lt;property name="portlet" value="3.1"/&gt;
+    &lt;/fragment&gt;
+    			</source>
+    			</p>
+    			<p>defines which portlet to display. <tt>&lt;property name="portlet" value="3.1"/&gt;</tt> tells the Portal
+				to lookup the Portlet "3.1" and display it in this location. The value "3.1" means refers to the ids given
+				in <i>portletentityregistry.xml</i> (discussed previously). In this case, it mean application id "3",
+				portlet id "1".
+				</p>
+			</subsection>
+		</section>
+
+		<section name="Advanced Customization">
+			<subsection name="JSP Templates">
+				<p>It is possible to customize the JSP templates Pluto uses. This is beyond the scope of this document,
+				but a brief outline follows to get you started.</p>
+
+				<p>By default, Pluto uses JSP templates from the directory
+				${TOMCAT_HOME}/webapps/pluto/WEB-INF/aggregation directory. This can be overridden by
+				adding a line like
+				<source>
+aggregation.base.dir=/WEB-INF/templates/
+				</source>
+				to the file ${TOMCAT_HOME}/webapps/pluto/WEB-INF/config/services/ConfigService.properties.
+				</p>
+				<p>The following JSP files are used by the Portal:
+					<ul>
+						<li>Banner.jsp - The blue title bar which says "Pluto - Reference Implementation". Only called from RootFragment.jsp</li>
+						<li>ColumnFragment.jsp - Called for each column fragment.</li>
+						<li>Head.jsp - The HTML header. Only called from RootFragment.jsp</li>
+						<li>PageFragment.jsp - Called for each Portal page displayed.</li>
+						<li>PortletFragmentFooter.jsp - The footer of each Portlet.</li>
+						<li>PortletFragmentHeader.jsp - The header of each Portlet.</li>
+						<li>RootFragment.jsp - Defines the layout of the Portal. This is the file to modify if you need
+							to modify the width of the navigation bar, for instance.</li>
+						<li>RowFragment.jsp - Called for each row fragment.</li>
+						<li>TabNavigation.jsp - Displays the navigation menu.</li>
+					</ul>
+				</p>
+				<p>
+				Most customization of the Portal can be done in RootFragment.jsp,
+				PortletFragmentHeader.jsp and PortletFragmentFooter.jsp.
+				</p>
+			</subsection>
+			<subsection name="Internationalization">
+				<p>The Pluto portal supports non latin-1 character-sets in its output. To enable this, uncomment the section
+				<source>
+	 &lt;init-param&gt;
+	     &lt;param-name&gt;charset&lt;/param-name&gt;
+	     &lt;param-value&gt;utf-8&lt;/param-value&gt;
+	 &lt;/init-param&gt;
+				</source>
+				from the "pluto" Servlet section in the file ${TOMCAT_HOME}/webapps/pluto/WEB-INF/web.xml.</p>
+			</subsection>
+			<subsection name="Further Information">
+				<p>
+				Further information can be found in the <a href="../faq.html">FAQ</a>, on the <a href="../../mail-lists.html">Mailing Lists</a>
+				and on the <a href="../../wiki.html">Wiki</a>
+				</p>
+			</subsection>
+		</section>
+	</body>
+</document>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v101/userguide/portal.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v101/userguide/portal.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: portals/pluto/trunk/src/site/xdoc/v101/userguide/testsuite.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v101/userguide/testsuite.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v101/userguide/testsuite.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v101/userguide/testsuite.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,35 @@
+<?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>User Guide: Testsuite</title>
+</properties>
+
+<body>
+<section name="Testsuite Overview">
+<p>
+
+</p>
+</section>
+
+
+</body>
+</document>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v101/userguide/testsuite.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v101/userguide/testsuite.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: portals/pluto/trunk/src/site/xdoc/v11/app-servers.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v11/app-servers.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v11/app-servers.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v11/app-servers.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,159 @@
+<?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>Supported Application Servers</title>
+  </properties>
+  
+  <body>
+    <section name="Supported Application Servers">
+      <p>The following application servers have been tested with Pluto 1.1:</p>
+      <p>
+        <table>
+          <tr>
+            <th>App Server</th>
+            <th>Version</th>
+            <th>Status</th>
+            <th>Notes</th>
+          </tr>
+          <tr>
+            <td>Tomcat</td>
+            <td>5.5.9</td>
+            <td>WORKING</td>
+            <td>
+              Use <code>mvn pluto:install -DinstallDir=/path/to/tomcat</code> 
+              to install the container and portal into Tomcat.  Make sure
+              the &lt;Connector&gt; element in Tomcat's conf/server.xml file
+              has the attribute <code>emptySessionPath=true</code> set.
+            </td>
+          </tr>
+          <tr>
+            <td>Tomcat</td>
+            <td>5.5.12</td>
+            <td>MANUAL</td>
+            <td>
+              Tomcat contains a bug and does not recognize the context
+              configuration.  Manual Installation and renaming will work.
+            </td>
+          </tr>
+          <tr>
+            <td>Tomcat</td>
+            <td>5.5.17</td>
+            <td>Working</td>
+            <td>
+              Use <code>mvn pluto:install -DinstallDir=/path/to/tomcat</code> 
+              to install the container and portal into Tomcat.
+            </td>
+          </tr>
+          <tr>
+            <td>Tomcat</td>
+            <td>5.5.20</td>
+            <td>Working</td>
+            <td>
+              Use <code>mvn pluto:install -DinstallDir=/path/to/tomcat</code> 
+              to install the container and portal into Tomcat.
+            </td>
+          </tr>
+          <tr>
+            <td>Tomcat</td>
+            <td>5.5.23</td>
+            <td>Working</td>
+            <td>
+              Use <code>mvn pluto:install -DinstallDir=/path/to/tomcat</code> 
+              to install the container and portal into Tomcat.
+            </td>
+          </tr>
+          <tr>
+            <td>Tomcat</td>
+            <td>6.0.13</td>
+            <td>Working</td>
+            <td>
+              Use <code>mvn pluto:install -DinstallDir=/path/to/tomcat</code> 
+              to install the container and portal into Tomcat.  Make sure
+              the &lt;Connector&gt; element in Tomcat's conf/server.xml file
+              has the attribute <code>emptySessionPath=true</code> set.
+            </td>
+          </tr>
+          <tr>
+            <td>Tomcat</td>
+            <td>5.5.20</td>
+            <td>Working</td>
+            <td>
+              Use <code>mvn pluto:install -DinstallDir=/path/to/tomcat</code> 
+              to install the container and portal into Tomcat.  Make sure
+              the &lt;Connector&gt; element in Tomcat's conf/server.xml file
+              has the attribute <code>emptySessionPath=true</code> set.
+            </td>
+          </tr>
+          <tr>
+            <td>Tomcat</td>
+            <td>5.5.23</td>
+            <td>Working</td>
+            <td>
+              Use <code>mvn pluto:install -DinstallDir=/path/to/tomcat</code> 
+              to install the container and portal into Tomcat.  Make sure
+              the &lt;Connector&gt; element in Tomcat's conf/server.xml file
+              has the attribute <code>emptySessionPath=true</code> set.
+            </td>
+          </tr>
+          <tr>
+            <td>Tomcat</td>
+            <td>6.0.13</td>
+            <td>Working</td>
+            <td>
+              Use <code>mvn pluto:install -DinstallDir=/path/to/tomcat</code> 
+              to install the container and portal into Tomcat.  Make sure
+              the &lt;Connector&gt; element in Tomcat's conf/server.xml file
+              has the attribute <code>emptySessionPath=true</code> set.
+            </td>
+          </tr>
+          <tr>
+            <td>Sun Java System Application Server (Glassfish)</td>
+            <td>9.1 build 25</td>
+            <td>WORKING</td>
+            <td>Installation instructions are <a href="http://wiki.apache.org/portals/Pluto/InstallPlutoGlassfish">here</a> on the Pluto wiki.</td>
+          </tr>
+          <tr>
+            <td>Jetty</td>
+            <td>5.1.5rc2</td>
+            <td>BEING FIXED</td>
+            <td>Deployment Descriptor Error. See Issue Log.</td>
+          </tr>
+          <tr>
+            <td>WebLogic</td>
+            <td></td>
+            <td>UNTESTED</td>
+            <td></td>
+          </tr>
+          <tr>
+            <td>WebSphere</td>
+            <td></td>
+            <td>UNTESTED</td>
+            <td></td>
+          </tr>
+        </table>
+      </p>
+    </section>
+  </body>
+  
+</document>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v11/app-servers.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v11/app-servers.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: portals/pluto/trunk/src/site/xdoc/v11/architecture.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v11/architecture.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v11/architecture.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v11/architecture.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,38 @@
+<?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>Architectural Diagrams</title>
+  </properties>
+  
+  <body>
+    <section name="Architectural Diagrams">
+      <p>
+        The following diagram depicts the architectural
+        components of Pluto 1.1 and 2.0. More details coming soon.
+        <img src="../images/architecture.png"/>
+      </p>
+    </section>
+  </body>
+  
+</document>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v11/architecture.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v11/architecture.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: portals/pluto/trunk/src/site/xdoc/v11/deploying.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v11/deploying.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v11/deploying.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v11/deploying.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,284 @@
+<?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 Portlet to Pluto Portal</title>
+  </properties>
+  
+  <body>
+    
+    <section name="Deploying Portlet to Pluto Portal">
+      
+      <p>
+        There are 2 steps involved in deploying a portlet application in Pluto 1.1 or 2.0:
+        <ul>
+          <li>
+            <b>Assembly</b>: All portlet applications must be run through the
+            pluto assembler before being deployed. The assembly process injects
+            pluto specific information for deployment. Specifically, a servlet
+            and servlet mapping are added to the deployment descriptor (web.xml). 
+            This servlet (<code>org.apache.pluto.core.PortletServlet</code>) will be 
+            used to dispatch portlet requests to the portlet application.
+          </li>
+          <li>
+            <b>Deployment</b>: After portlet applications are assembled properly
+            they must be deployed to the servlet engine within which the portal
+            application is running. The current bundled distribution uses
+            Tomcat 5.5 as the servlet engine.
+          </li>
+        </ul>
+      </p>
+      
+      <subsection name="Portlet Assembly">
+        <p>
+            The maven-pluto-plugin can be used to assemble a portlet application war.
+            It will place the proper <code>PortletServlet</code> configuration in web.xml.
+        </p>
+        <p>          
+          The custom Maven 2 build shown below requires
+          a Tomcat context deployment descriptor that has the same name as your
+          artifactId with an xml extension (e.g. HelloWorldPortlet.xml).
+        </p>
+        <p>
+          To properly assemble your portlet using the Maven 2 plugin,
+          your project's directory structure and artifact placement must conform to Maven's standard:
+        </p>
+        <p>
+          <source><![CDATA[
+	HelloWorldPortlet (top level directory)
+	|- pom.xml (the pom file)
+	|- src (Subdir containing main subdirectory)
+	    |- main (Subdir containing java, resources and webapp subdirs)
+	    	|- java (java source code goes under here)
+		    |       `- com
+		    |           `- mycompany
+		    |               `- portlet
+		    |                   `- HelloWorldPortlet.java (portlet source)
+		    |- webapp  (webapp resources (jsp, css, images) go under here)
+		    	`- jsp 
+		    		`- HelloWorldPortletView.jsp (for view mode)		    			    
+		    		`- HelloWorldPortletEdit.jsp (for edit mode)		    			    
+		    	`- META-INF
+		    		`- HelloWorldPortlet.xml (Tomcat context deployment descriptor)
+		    	`- WEB-INF
+			    	`- portlet.xml (JSR-168 deployment descriptor)
+			    	`- web.xml (This will be modified by maven-pluto-plugin)
+          ]]></source>
+        </p>
+
+        <p>
+        This is an example of what the Tomcat context deployment descriptor will contain:
+          <source><![CDATA[
+		<Context path="/HelloWorldPortlet"
+			docBase="HelloWorldPortlet" 
+			crossContext="true"/>
+          ]]></source>
+        </p>
+        <p>
+        To configure the maven-pluto-plugin, you must configure it in your pom.
+        For easy of setup, use this as you pom file, changing the groupId, artifactId and version
+        to values appropriate to your custom portlet.
+          <source><![CDATA[
+<project xmlns="http://maven.apache.org/POM/4.0.0"
+         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+  
+  <!-- Change this to something akin to your java package structure -->
+  <groupId>com.mycompany.portlet</groupId>
+  <modelVersion>4.0.0</modelVersion>
+  <!-- Version of this app -->
+  <version>0.1-alpha1</version>
+  <!-- Base name of the war file without .war ext -->
+  <artifactId>HelloWorldPortlet</artifactId>
+  <packaging>war</packaging>
+  <name>${pom.artifactId}</name>
+  <!-- Dependency Version Properties ======================================= -->
+  <properties>
+    <!-- Change this to 2.0.0 for Pluto 2.0 or to another appropriate version -->
+    <pluto.version>1.1.4</pluto.version>
+    <portlet-api.version>1.0</portlet-api.version>
+    <servlet-api.version>2.4</servlet-api.version>
+    <jsp-api.version>2.0</jsp-api.version>
+    <junit.version>3.8.1</junit.version>
+  </properties>  
+  <dependencies>
+    <dependency>
+      <groupId>javax.portlet</groupId>
+      <artifactId>portlet-api</artifactId>
+      <version>${portlet-api.version}</version>
+      <scope>provided</scope><!-- Prevents addition to war file -->
+    </dependency>
+    <dependency>
+      <groupId>javax.servlet</groupId>
+      <artifactId>servlet-api</artifactId>
+      <version>${servlet-api.version}</version>
+      <scope>provided</scope>
+    </dependency>
+    <dependency>
+      <groupId>junit</groupId>
+      <artifactId>junit</artifactId>
+      <version>${junit.version}</version>
+      <scope>test</scope>
+    </dependency>
+    <dependency>
+      <groupId>org.apache.pluto</groupId>
+      <artifactId>pluto-util</artifactId>
+      <version>${pluto.version}</version>
+      <scope>provided</scope>
+    </dependency>
+    <!-- Any other build or deployment dependancies go here -->
+  </dependencies>
+  <build>
+    <finalName>${pom.name}</finalName>
+    <plugins>
+      <!-- configure to use Java 6 to compile (change to your JDK) --> 
+      <plugin>
+          <groupId>org.apache.maven.plugins</groupId>
+          <artifactId>maven-compiler-plugin</artifactId>
+          <configuration>
+              <source>1.6</source>
+              <target>1.6</target>
+          </configuration>
+       </plugin>
+      <!-- configure maven-war-plugin to use updated web.xml -->
+      <plugin>
+        <artifactId>maven-war-plugin</artifactId>
+        <configuration>
+          <webXml>${project.build.directory}/pluto-resources/web.xml</webXml>
+        </configuration>
+      </plugin>
+      <!-- bind 'pluto:assemble' goal to 'generate-resources' lifecycle -->
+      <plugin>
+        <groupId>org.apache.pluto</groupId>
+        <artifactId>maven-pluto-plugin</artifactId>
+        <version>${pluto.version}</version>
+        <executions>
+          <execution>
+            <phase>generate-resources</phase>
+            <goals>
+              <goal>assemble</goal>
+            </goals>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+  
+</project>
+          ]]></source>
+        </p>        
+        <p>
+            Once configured, the war generated by an 'mvn package' (or install) command will contain
+            the appropriate pluto configuration.
+        </p>
+      </subsection>
+
+        <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/fragments/portlet.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/fragments/portlet.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>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v11/deploying.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v11/deploying.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: portals/pluto/trunk/src/site/xdoc/v11/getting-started.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v11/getting-started.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v11/getting-started.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v11/getting-started.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,281 @@
+<?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</title>
+  </properties>
+  
+  <body>
+
+    <section name="Installing the Pluto 1.1 Binary Build">
+      <div class="highlightBox">
+        <h4>About Pluto Distributions</h4>
+        <p>
+            Currently, only Pluto 1.1 has a binary distribution.
+        </p>
+        <p>
+          There are a number of distributions to choose from depending
+          on your needs.
+          <ul>
+            <li><strong>pluto-current-bundle</strong> - Provides Pluto and Tomcat bundled together.
+                If you are getting started with Pluto, this is the distribution you
+                want.</li>
+            <li><strong>pluto-current-bin</strong> - Provides the Pluto libraries, portal and 
+                testsuite web applications.  Includes ant tasks.</li>
+            <li><strong>pluto-current-container-bin</strong> - Provides the Pluto container
+                libraries only.</li>
+            <li><strong>pluto-current-src</strong> - Provides the Pluto source code; requires
+                that you build and deploy Pluto on your own.</li>
+          </ul>
+        </p>
+      </div>
+      <ol>
+        <li>Download the Pluto 1.1 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>&lt;PLUTO-1.1-HOME&gt; will be the top level directory.</li>
+        	</ol>	
+        <li>Execute startup.bat (Windows) or startup.sh (Unix)
+in &lt;PLUTO-1.1-HOME&gt;/bin.</li>
+			<ol>
+	        	<li>Use shutdown.bat/shutdown.sh to stop the portal</li>
+			</ol>
+        <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=tomcat).</li>
+      </ol>
+
+    </section>
+	    
+    <section name="Building Pluto 1.1 and 2.0 from Source">
+      
+      <p>
+        Maven 2 is utilized as the project management and build system for
+        Pluto 1.1 and 2.0. Pluto currently provides Maven plugins which can be used to
+        install the Pluto Portal, assemble portlet applications, deploy
+        applications, and publish portlet applications to the Pluto Portal.
+      </p>
+
+      <subsection name="Obtaining Pluto 1.1/2.0 Source Code">
+		<p>The Pluto project uses the
+		<a href="http://subversion.tigris.org/">Subversion</a> version control
+		system.  If you're new to Subversion, you can check out the
+		<a href="http://svnbook.red-bean.com/">online book</a> about Subversion.
+		Note that we are currently using Subversion 1.3.x (there are separate
+		versions of the book covering the different versions of Subversion). 
+		</p>
+
+    	<p><b>Web Access to Subversion</b></p>
+    	
+		<p>
+		To browse the Pluto source code, you can use the
+		<a href="http://svn.apache.org/viewcvs.cgi/portals/pluto/trunk?root=Apache-SVN">ViewCVS
+		web interface</a> to Subversion. This is current at all times.
+		</p>
+
+		<p><b>Normal Subversion Access</b></p>
+		<p>Anyone can check code out of Subversion anonymously.  However, you need to specify a
+		username and password in order to update the Subversion repository, and only
+		Pluto committers have the permissions to do that.  We run Subversion
+		over standard HTTPS, so hopefully you won't have problems with intervening
+		firewalls.</p>
+
+		<h3>Check out from Subversion</h3>
+		
+		<p>Again, anyone can do this.  To check out the latest distribution of Pluto 2.0 (trunk) to a directory 
+		called 'pluto' use this command:
+		<pre>svn checkout https://svn.apache.org/repos/asf/portals/pluto/trunk/ pluto</pre>
+		</p>
+
+		<p>To check out Pluto 1.1.<code>x</code> source to the 'pluto' directory use this command (substituting '<code>x</code>' for the 
+        current release number, e.g. 1.1.<code>5</code>):
+		<pre>svn checkout https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.x pluto</pre>
+		</p>
+
+        <p>
+          Zipped up Pluto 1.1 source distributions can also be downloaded from
+        a <a href="http://www.apache.org/dyn/closer.cgi/portals/pluto/">distribution mirror</a>.  
+        </p>          
+
+	  </subsection>	    
+	    
+      <subsection name="Building Pluto with Maven 2">
+        <p>
+          If this is your first time building Pluto with Maven 2, edit <code>~/.m2/settings.xml</code>
+	  and add the &lt;pluginGroups&gt; element:
+	  <p>
+	    <source><![CDATA[
+<settings>
+  ...
+  <pluginGroups>
+    <pluginGroup>org.apache.pluto</pluginGroup>
+  </pluginGroups>
+  ...
+</settings>]]>
+            </source>
+	  </p>
+          If you don't have <code>org.apache.pluto</code> specified as a <code>&lt;pluginGroup&gt;</code>,
+	  then the <code>pluto:install</code> will fail.
+	</p>
+        <p>
+          <code>&lt;PLUTO_SRCHOME&gt;</code> is the local directory where the
+          Pluto 1.1/2.0 source distribution has been checked out or unzipped into.
+        </p>
+        <p>
+          <source><![CDATA[
+$> cd <PLUTO_SRCHOME>
+$> mvn install
+$> mvn pluto:install -DinstallDir=path/to/appserver
+          ]]></source>
+        </p>
+        <p>
+          The <code>install</code> goal is a built in Maven 2 lifecycle
+          which builds the project artifacts and installs them into the Maven
+          repository.
+        </p>
+        <p>
+          The <code>pluto:install</code> goal will take the resulting artifacts
+          and properly deploy them within the configured Tomcat installation.
+          Currently, the Pluto install has been tested on Tomcat 5.5.9, 5.5.17 and 5.5.20, 5.5.23, and 6.0.13.
+          The Tomcat 5 archive can be found <a href="http://archive.apache.org/dist/tomcat/tomcat-5/archive">here</a>.
+        </p>
+        <p>
+          If installing to a directory that contains spaces, <code>installDir</code>
+          needs to be enclosed within quotes:
+        </p>
+        <p>
+          <source><![CDATA[
+C:\pluto> mvn pluto:install -DinstallDir="C:\Program Files\Apache Software Foundation\Tomcat 5.5"
+          ]]></source>
+        </p>
+        
+      </subsection>
+      
+      <subsection name="Installing Pluto Manually">
+        <p>
+        This section documents the manual installation of Pluto 1.1 and 2.0 into Tomcat. It replaces 
+        the pluto:install goal, but requires that the built-in Maven 2 install goal 
+        (<code>mvn install</code>) be run from <code>&lt;PLUTO_SRCHOME&gt;</code>.
+        </p>
+        <p>
+          <b>Step 1:</b>
+          <source><![CDATA[
+$> cd <PLUTO_SRCHOME>
+$> mvn install
+          ]]></source>
+        </p>
+        <p>
+          <b>Step 2:</b> Copy the following to
+          <code>&lt;TOMCAT_HOME&gt;/shared/lib</code>:
+          <ul>
+            <li>activation-1.1.jar (Pluto 2.0 only)</li>
+            <li>castor-1.1.1.jar (Pluto 1.1.x only)</li>
+            <li>portlet-api-1.0.jar or portlet-api-2.0.jar</li>
+            <li>jaxb-api-2.1.jar (Pluto 2.0 only)</li>
+            <li>jaxb-impl-2.1.2.jar (Pluto 2.0 only)</li>
+            <li>ccpp-1.0.jar (Pluto 2.0 only)</li>
+            <li>stax-1.2.0.jar (Pluto 2.0 only)</li>
+            <li>stax-api-1.0.1.jar (Pluto 2.0 only)</li>
+            <li>xercesImpl-2.6.2.jar (Pluto 2.0 only)</li>
+            <li>xmlParserAPIs-2.6.2.jar (Pluto 2.0 only)</li>
+            <li>pluto-container-x.x.x.jar (x.x.x is the version of Pluto you built)</li>
+            <li>pluto-descriptor-api-x.x.x.jar (x.x.x is the version of Pluto you built)</li>
+            <li>pluto-descriptor-impl-x.x.x.jar (x.x.x is the version of Pluto you built)</li>
+            <li>pluto-taglib-x.x.x.jar (x.x.x is the version of Pluto you built)</li>
+          </ul>
+        </p>
+        <p>
+          <b>Step 3:</b> For platforms running on Java 1.4 and Pluto 1.1, copy the following to
+          <code>&lt;TOMCAT_HOME&gt;/common/endorsed</code> (if you are running Java 1.5+, or you are 
+          running Pluto 2.0, it is recommended to skip this step):
+          <ul>
+            <li>xercesImpl-2.6.2.jar</li>
+            <li>xmlParserAPIs-2.6.2.jar</li>
+          </ul>
+        </p>
+        <p>
+          <b>Step 4:</b> Copy the following to
+          <code>&lt;TOMCAT_HOME&gt;/conf/Catalina/localhost</code>:
+          <ul>
+            <li>&lt;PLUTO_SRCHOME&gt;/pluto-portal/src/main/resources/pluto.xml</li>
+            <li>&lt;PLUTO_SRCHOME&gt;/pluto-testsuite/src/main/resources/testsuite.xml</li>
+          </ul>
+        </p>
+        <p>
+          <b>Step 5:</b> Copy the following to
+          <code>&lt;TOMCAT_HOME&gt;/webapps</code>:
+          <ul>
+            <li>&lt;PLUTO_SRCHOME&gt;/pluto-portal/target/pluto-portal.war</li>
+            <li>&lt;PLUTO_SRCHOME&gt;/pluto-testsuite/target/pluto-testsuite.war</li>
+          </ul>
+        </p>
+      </subsection>
+          
+    <subsection name="Configuring Source-Built Pluto for Application Scope PortletSession Attributes">
+    <p>To be able to use application-scoped <code>PortletSession</code> attributes in Pluto, modify
+    the Connector element for port 8080 in <code>&lt;TOMCAT_HOME&gt;/conf/server.xml</code> by
+    adding the following attribute and value: emptySessionPath="true".
+    </p>
+    </subsection>    
+    <subsection name="Configuring User and Role in the Pluto Source Build">
+      <p>
+        The Pluto Testsuite portlet application needs the role '<code>pluto</code>'
+        to run the Security Mapping Test. So before starting tomcat, you should
+        edit <code>&lt;TOMCAT_HOME&gt;/conf/tomcat-users.xml</code>, add the
+        role '<code>pluto</code>', and add a user in that role. The simplest way
+        to do this is to edit add the '<code>pluto</code>' role to the
+        '<code>tomcat</code>' user's record. Here is a sample
+        <code>tomcat-users.xml</code> file:
+        <source><![CDATA[
+<?xml version="1.0" encoding="utf-8"?>
+<tomcat-users>
+  <role rolename="manager"/>
+  <role rolename="pluto"/>
+  <role rolename="tomcat"/>
+  <role rolename="role1"/>
+  <user username="tomcat" password="tomcat" roles="tomcat,pluto,manager"/>
+  <user username="role1" password="tomcat" roles="role1"/>
+  <user username="both" password="tomcat" roles="tomcat,role1"/>
+  <user username="pluto" password="pluto" roles="pluto,manager"/>
+</tomcat-users>
+        ]]></source>
+      </p>
+    </subsection>
+    
+    
+    <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 and password you just created in <code>tomcat-users.xml</code>.
+        If you added the 'pluto' role to the 'tomcat' user's record, you can
+        login as 'tomcat/tomcat'.
+      </p>
+    </subsection>
+    </section>
+    
+  </body>
+  
+</document>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v11/getting-started.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v11/getting-started.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml

Added: portals/pluto/trunk/src/site/xdoc/v11/release-notes.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/src/site/xdoc/v11/release-notes.xml?rev=642585&view=auto
==============================================================================
--- portals/pluto/trunk/src/site/xdoc/v11/release-notes.xml (added)
+++ portals/pluto/trunk/src/site/xdoc/v11/release-notes.xml Sat Mar 29 12:05:20 2008
@@ -0,0 +1,164 @@
+<?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>Release Notes</title>
+  </properties>
+  
+  <body>
+    <section name="Pluto 1.1.5 Release Notes">
+      <subsection name="Bug">
+        <ul>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-356'>PLUTO-356</a> - Pluto Driver not using injected Portal URL Parser</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-361'>PLUTO-361</a> - Error when parsing the portal url</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-397'>PLUTO-397</a> - Copyright at bottom of Portal Driver content needs to be updated to 2007</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-399'>PLUTO-399</a> - Link and documentation on source-repository.html page is incorrect</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-421'>PLUTO-421</a> - PortletRequest.getParameterMap() must return an unmodifiable map (PLT.11.1.1)</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-439'>PLUTO-439</a> - Assembly code cannot parse Servlet 2.4 web.xml containing &lt;jsp-config&gt; tags</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-446'>PLUTO-446</a> - No way to set default page encoding for Pluto</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-447'>PLUTO-447</a> - Old version of junit included via commons-cli in pluto-util</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-448'>PLUTO-448</a> - No way to know if expiration cache value was set via PortletDD</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-449'>PLUTO-449</a> - portlet-skin.jsp does not have the JSTL core taglib directive</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-450'>PLUTO-450</a> - ExternalAppScopedAttributeTest.jsp has a minor javascript error</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-451'>PLUTO-451</a> - JSP21ExpressionEvaluatorProxy is causing an exception in Tomcat 6.0 if compiled using JDK 5.0</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-452'>PLUTO-452</a> - Assembler ant task fails on WAR with no manifest</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-455'>PLUTO-455</a> - Assembler emitts non-validating web.xml for servlet 2.3 and 2.4</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-457'>PLUTO-457</a> - PortletContainerException doesn't chain Throwable</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-460'>PLUTO-460</a> - PortletPreferenceDD doesn't descriminate between no (null) values and empty values (new String[0])</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-461'>PLUTO-461</a> - AbstractVersionedWebAppDescriptorTest based tests may fails based on available XML libraries</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-462'>PLUTO-462</a> - isPortletModeAllowed and isWindowStateAllowed do case-sensitve checks</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-473'>PLUTO-473</a> - XML Schema Location for pluto-portal-driver-config.xsd points to obsolete schema definition</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-474'>PLUTO-474</a> - CLONE -portlet session should not be invalidated when lastAccessedTime is 0</li>
+            <li><a href='https://issues.apache.org/jira/browse/PLUTO-475'>PLUTO-475</a> - Default Portlet Skin and WindowStateAnchorTag emit invalid markup</li>
+        </ul>
+      </subsection>
+      <subsection name="Improvement">
+        <ul>
+           <li><a href='https://issues.apache.org/jira/browse/PLUTO-360'>PLUTO-360</a> - FileAssemblerTest cannot be executed offline</li>
+           <li><a href='https://issues.apache.org/jira/browse/PLUTO-394'>PLUTO-394</a> - o.a.p.tags.el.ParamTag does not evaluate EL on &quot;name&quot; attribute</li>
+           <li><a href='https://issues.apache.org/jira/browse/PLUTO-417'>PLUTO-417</a> - PortletResponseImpl doesn't allow wsrp rewrite urls</li>
+           <li><a href='https://issues.apache.org/jira/browse/PLUTO-456'>PLUTO-456</a> - fix line endings on files.</li>
+           <li><a href='https://issues.apache.org/jira/browse/PLUTO-458'>PLUTO-458</a> - Improve exception handling with AbstractCastorDescriptorService</li>
+           <li><a href='https://issues.apache.org/jira/browse/PLUTO-465'>PLUTO-465</a> - Automatic determination of JAXP usage</li>
+           <li><a href='https://issues.apache.org/jira/browse/PLUTO-472'>PLUTO-472</a> - Fix Pluto Maven 2 release assemblies so they actually work.</li>
+        </ul>
+      </subsection>
+    </section>
+      
+    <section name="Pluto 1.1.4 Release Notes">
+      <subsection name="Bug">
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-341'>PLUTO-341</a> - Page Admin Portlet does not work with Internet Explorer ver 6</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-356'>PLUTO-356</a> - Pluto Driver not using injected Portal URL Parser</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-361'>PLUTO-361</a> - Error when parsing the portal url</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-369'>PLUTO-369</a> - Inconsistency in PortletRequest attribute handling</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-370'>PLUTO-370</a> - Cannot build 1.1.3 GA release from source</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-381'>PLUTO-381</a> - Not able to Add Portal page to a new application</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-383'>PLUTO-383</a> - DefaultUserInfo service returns null userinfo map</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-386'>PLUTO-386</a> - Src distribution does not contain Pluto-AntTask.jar</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-389'>PLUTO-389</a> - Pluto-Ant-Task can not be built because of missing junit dependency</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-390'>PLUTO-390</a> - EarAssemblerTest failure</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-393'>PLUTO-393</a> - Maximize Window State formatting problems in Firefox 2.0</li>
+        </ul>
+      </subsection>
+      <subsection name="Improvement"> 
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-347'>PLUTO-347</a> - Remove dependency on shared/lib xerces and xmlAPIs</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-358'>PLUTO-358</a> - Upgrade to Castor 1.1.1</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-375'>PLUTO-375</a> - The ExpressionEvaluatorProxy for JSP 2.1 is unimplemented</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-376'>PLUTO-376</a> - Update Pluto to work with Tomcat 6.x</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-384'>PLUTO-384</a> - PortletContextManager.getPortletApplicationDescriptor returns null when a portlet context cannot be found.</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-385'>PLUTO-385</a> - Use CSS-based tab navigation for Pluto Portal</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-387'>PLUTO-387</a> - Provide add/remove page functionality to Pluto Portal Driver</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-388'>PLUTO-388</a> - Removed use of deprecated method</li>
+        </ul>
+      </subsection>
+      <subsection name="New Feature"> 
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-186'>PLUTO-186</a> - ToolTips to Portlet Controls</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-359'>PLUTO-359</a> - Add ability to assemble EAR files</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-382'>PLUTO-382</a> - Have Page Administrator portlet persist new page configurations</li>
+        </ul>
+      </subsection>
+    </section>
+
+    <section name="Pluto 1.1.3 Release Notes">
+      <subsection name="Bug">
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-351'>PLUTO-351</a> - Method removeAttribute in PortletRequestImpl causes NullPointerException in Resin 3.0.17 </li>
+        </ul>
+      </subsection> 
+      
+      <subsection name="Improvement">
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-350'>PLUTO-350</a> - Remove absolute url dependency</li>
+        </ul>
+      </subsection>
+   
+      <subsection name="New Feature">
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-352'>PLUTO-352</a> - Implement "Simple" Portlet Page Support</li>
+        </ul>
+      </subsection>
+          
+      <subsection name="Task">
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-348'>PLUTO-348</a> - Automate PGP key signing of M2 artifacts.</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-349'>PLUTO-349</a> - Include META-INF/LICENSE and META-INF/NOTICE in maven artifacts</li>
+        </ul>
+      </subsection>    
+    </section>
+
+    <section name="Pluto 1.1.2 Release Notes">
+
+      <subsection name="Bug">
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-331'>PLUTO-331</a> - Page Admin Portlet fails in Pluto 1.1.1</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-332'>PLUTO-332</a> - PortletContextManager.remove(InternalPortletContext) fails</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-336'>PLUTO-336</a> - Provide alternate ways for deriving applicationId</li>
+        </ul>
+      </subsection>    
+      <subsection name="Improvement">
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-334'>PLUTO-334</a> - UserInfoService should provide PortletWindow in getUserInfo()</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-335'>PLUTO-335</a> - Use proper namespacing for JavaScript in Page Admin Portlet</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-338'>PLUTO-338</a> - Remove dependency to plexus file utils, commons httpclient and commons beanutils</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-344'>PLUTO-344</a> - Update maven pluto plugin to accept a list of war files to assemble.</li>
+        </ul>
+      </subsection>    
+      <subsection name="New Feature">
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-328'>PLUTO-328</a> - Add support for a callback right before Render and Action in PortletServlet</li>
+        </ul>
+      </subsection>                
+      <subsection name="Task">
+        <ul>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-339'>PLUTO-339</a> - Deprecate PortletEntity getControllerServletUri() so it can be removed in future versions of Pluto.</li>
+          <li><a href='https://issues.apache.org/jira/browse/PLUTO-345'>PLUTO-345</a> - Fix link to distribution website on http://portals.apache.org/pluto/v11/getting-started.html</li>
+        </ul>
+      </subsection> 
+    </section>
+	    
+  </body>
+  
+</document>
+

Propchange: portals/pluto/trunk/src/site/xdoc/v11/release-notes.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/pluto/trunk/src/site/xdoc/v11/release-notes.xml
------------------------------------------------------------------------------
    svn:mime-type = text/xml



Mime
View raw message