Modified: portals/site-live/pluto/v11/deploying.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v11/deploying.html?rev=1834161&r1=1834160&r2=1834161&view=diff ============================================================================== --- portals/site-live/pluto/v11/deploying.html (original) +++ portals/site-live/pluto/v11/deploying.html Fri Jun 22 19:35:14 2018 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2017-01-13 + Last Published: 2018-06-22 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -105,6 +105,10 @@ </li> <li class="none"> + <a href="../security.html">Security</a> + </li> + + <li class="none"> <a href="../status.html">Status</a> </li> @@ -136,27 +140,27 @@ <ul> <li class="none"> - <a href="../v30/getting-started.html">Getting Started</a> + <a href="../v301/getting-started.html">Getting Started</a> </li> <li class="none"> - <a href="../v30/deploying.html">Deploying Portlets</a> + <a href="../v301/deploying.html">Deploying Portlets</a> </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet Concepts</a> + <a href="../v301/portlet-api.html">Portlet Concepts</a> </li> <li class="none"> - <a href="../v30/v3Features.html">Version 3 Features</a> + <a href="../v301/v3Features.html">Version 3 Features</a> </li> <li class="none"> - <a href="../v30/tck.html">Using the TCK</a> + <a href="../v301/tck.html">Using the TCK</a> </li> <li class="none"> - <a href="../v30/release-notes.html">Release Notes</a> + <a href="../v301/release-notes.html">Release Notes</a> </li> </ul> <h5>Pluto 2.0</h5> @@ -250,7 +254,7 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Deploying_Portlet_to_Pluto_Portal"></a>Deploying Portlet to Pluto Portal</h2> + <div class="section"><h2><a name="Deploying_Portlet_to_Pluto_Portal"></a>Deploying Portlet to Pluto Portal</h2> <p> There are 2 steps involved in deploying a portlet application in Pluto 1.1: <ul><li><b>Assembly</b>: All portlet applications must be run through the @@ -259,28 +263,28 @@ 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> <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> -<div class="section"><h3><a name="Portlet_Assembly"></a>Portlet Assembly</h3> + </li> +</ul> +</p> +<div class="section"><h3><a name="Portlet_Assembly"></a>Portlet Assembly</h3> <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> <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> <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> <p><div class="source"><pre> HelloWorldPortlet (top level directory) |- pom.xml (the pom file) @@ -300,18 +304,18 @@ `- WEB-INF `- portlet.xml (JSR-168 deployment descriptor) `- web.xml (This will be modified by maven-pluto-plugin) - </pre> -</div> -</p> + </pre> +</div> +</p> <p> This is an example of what the Tomcat context deployment descriptor will contain: <div class="source"><pre> <Context path="/HelloWorldPortlet" docBase="HelloWorldPortlet" crossContext="true"/> - </pre> -</div> -</p> + </pre> +</div> +</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 @@ -402,15 +406,15 @@ </build> </project> - </pre> -</div> -</p> + </pre> +</div> +</p> <p> Once configured, the war generated by an 'mvn package' (or install) command will contain the appropriate pluto configuration. - </p> -</div> -<div class="section"><h3><a name="Portlet_Deployment"></a>Portlet Deployment</h3> + </p> +</div> +<div class="section"><h3><a name="Portlet_Deployment"></a>Portlet Deployment</h3> <p> To deploy a portlet application, simply deploy the application war using any standard mechanism for your application server. There are many @@ -418,12 +422,12 @@ 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> <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> + </p> <div class="source"><pre> <plugin> <artifactId>maven-antrun-plugin</artifactId> @@ -444,30 +448,30 @@ </execution> </executions> </plugin> - </pre> -</div> + </pre> +</div> <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> -</div> -<div class="section"><h3><a name="Portlet_Publishing"></a>Portlet Publishing</h3> + </p> +</div> +<div class="section"><h3><a name="Portlet_Publishing"></a>Portlet Publishing</h3> <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> +<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> <p> The page can then be configured by adding a <code>page</code> child element of the <code>render-config</code> element, like this: @@ -481,18 +485,18 @@ name="your_portlet_2"/> </page> </render-config> - </pre> -</div> -</p> + </pre> +</div> +</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> -</div> -</div> + </p> +</div> +</div> </div> </div> @@ -501,7 +505,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2017 + 2004-2018 Apache Software Foundation
Modified: portals/site-live/pluto/v11/getting-started.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v11/getting-started.html?rev=1834161&r1=1834160&r2=1834161&view=diff ============================================================================== --- portals/site-live/pluto/v11/getting-started.html (original) +++ portals/site-live/pluto/v11/getting-started.html Fri Jun 22 19:35:14 2018 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2017-01-13 + Last Published: 2018-06-22 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -105,6 +105,10 @@ </li> <li class="none"> + <a href="../security.html">Security</a> + </li> + + <li class="none"> <a href="../status.html">Status</a> </li> @@ -136,27 +140,27 @@ <ul> <li class="none"> - <a href="../v30/getting-started.html">Getting Started</a> + <a href="../v301/getting-started.html">Getting Started</a> </li> <li class="none"> - <a href="../v30/deploying.html">Deploying Portlets</a> + <a href="../v301/deploying.html">Deploying Portlets</a> </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet Concepts</a> + <a href="../v301/portlet-api.html">Portlet Concepts</a> </li> <li class="none"> - <a href="../v30/v3Features.html">Version 3 Features</a> + <a href="../v301/v3Features.html">Version 3 Features</a> </li> <li class="none"> - <a href="../v30/tck.html">Using the TCK</a> + <a href="../v301/tck.html">Using the TCK</a> </li> <li class="none"> - <a href="../v30/release-notes.html">Release Notes</a> + <a href="../v301/release-notes.html">Release Notes</a> </li> </ul> <h5>Pluto 2.0</h5> @@ -250,71 +254,71 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Installing_the_Pluto_1.1_Binary_Build"></a>Installing the Pluto 1.1 Binary Build</h2> -<div class="highlightBox"><h4>About Pluto Distributions</h4> + <div class="section"><h2><a name="Installing_the_Pluto_1.1_Binary_Build"></a>Installing the Pluto 1.1 Binary Build</h2> +<div class="highlightBox"><h4>About Pluto Distributions</h4> <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> + want.</li> <li><strong>pluto-current-bin</strong> - Provides the Pluto libraries, portal and - testsuite web applications. Includes ant tasks.</li> + testsuite web applications. Includes ant tasks.</li> <li><strong>pluto-current-container-bin</strong> - Provides the Pluto container - libraries only.</li> + 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> + that you build and deploy Pluto on your own.</li> +</ul> +</p> </div><ol type="1"><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/"; class="externalLink">distribution site</a>.</li> -<li>Unzip the binary distribution into a directory.</li> -<ol type="1"><li><PLUTO-1.1-HOME> will be the top level directory.</li> -</ol> + a <a class="externalLink" href="http://www.apache.org/dyn/closer.cgi/portals/pluto/";>distribution site</a>.</li> +<li>Unzip the binary distribution into a directory.</li> +<ol type="1"><li><PLUTO-1.1-HOME> will be the top level directory.</li> +</ol> <li>Execute startup.bat (Windows) or startup.sh (Unix) -in <PLUTO-1.1-HOME>/bin.</li> -<ol type="1"><li>Use shutdown.bat/shutdown.sh to stop the portal</li> -</ol> -<li>Browse to <a href="http://localhost:8080/pluto/portal"; class="externalLink">http://localhost:8080/pluto/portal</a></li> -<li>Login as user pluto (password=pluto) or tomcat (password=tomcat).</li> -</ol> -</div> -<div class="section"><h2><a name="Building_Pluto_1.1_from_Source"></a>Building Pluto 1.1 from Source</h2> +in <PLUTO-1.1-HOME>/bin.</li> +<ol type="1"><li>Use shutdown.bat/shutdown.sh to stop the portal</li> +</ol> +<li>Browse to <a class="externalLink" 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> +</div> +<div class="section"><h2><a name="Building_Pluto_1.1_from_Source"></a>Building Pluto 1.1 from Source</h2> <p> Maven 2 is utilized as the project management and build system for Pluto 1.1. 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> -<div class="section"><h3><a name="Obtaining_Pluto_1.1_Source_Code"></a>Obtaining Pluto 1.1 Source Code</h3> + </p> +<div class="section"><h3><a name="Obtaining_Pluto_1.1_Source_Code"></a>Obtaining Pluto 1.1 Source Code</h3> <p>The Pluto project uses the - <a href="http://subversion.tigris.org/"; class="externalLink">Subversion</a> version control + <a class="externalLink" 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/"; class="externalLink">online book</a> about Subversion. + <a class="externalLink" 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> +<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"; class="externalLink">ViewCVS + <a class="externalLink" 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> +<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> + firewalls.</p> <h3>Check out from Subversion</h3><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> + <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/"; class="externalLink">distribution mirror</a>. - </p> -</div> -<div class="section"><h3><a name="Building_Pluto_with_Maven_2"></a>Building Pluto with Maven 2</h3> + a <a class="externalLink" href="http://www.apache.org/dyn/closer.cgi/portals/pluto/";>distribution mirror</a>. + </p> +</div> +<div class="section"><h3><a name="Building_Pluto_with_Maven_2"></a>Building Pluto with Maven 2</h3> <p> If this is your first time building Pluto with Maven 2, edit <code>~/.m2/settings.xml</code> and add the <pluginGroups> element: @@ -326,90 +330,90 @@ in <PLUTO-1.1-HOME>/bin.</li> </pluginGroups> ... </settings> - </pre> -</div> -</p> + </pre> +</div> +</p> If you don't have <code>org.apache.pluto</code> specified as a <code><pluginGroup></code>, then the <code>pluto:install</code> will fail. - </p> + </p> <p><code><PLUTO_SRCHOME></code> is the local directory where the Pluto 1.1 source distribution has been checked out or unzipped into. - </p> + </p> <p><div class="source"><pre> $> cd <PLUTO_SRCHOME> $> mvn install $> mvn pluto:install -DinstallDir=path/to/appserver - </pre> -</div> -</p> + </pre> +</div> +</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> <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"; class="externalLink">here</a>. - </p> + The Tomcat 5 archive can be found <a class="externalLink" 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> <p><div class="source"><pre> C:\pluto> mvn pluto:install -DinstallDir="C:\Program Files\Apache Software Foundation\Tomcat 5.5" - </pre> -</div> -</p> -</div> -<div class="section"><h3><a name="Installing_Pluto_Manually"></a>Installing Pluto Manually</h3> + </pre> +</div> +</p> +</div> +<div class="section"><h3><a name="Installing_Pluto_Manually"></a>Installing Pluto Manually</h3> <p> This section documents the manual installation of Pluto 1.1 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><PLUTO_SRCHOME></code>. - </p> + </p> <p><b>Step 1:</b><div class="source"><pre> $> cd <PLUTO_SRCHOME> $> mvn install - </pre> -</div> -</p> + </pre> +</div> +</p> <p><b>Step 2:</b> Copy the following to <code><TOMCAT_HOME>/shared/lib</code>: - <ul><li>castor-1.1.1.jar (Pluto 1.1.x only)</li> -<li>portlet-api-1.0.jar</li> -<li>pluto-container-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> + <ul><li>castor-1.1.1.jar (Pluto 1.1.x only)</li> +<li>portlet-api-1.0.jar</li> +<li>pluto-container-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><TOMCAT_HOME>/common/endorsed</code> (if you are running Java 1.5+, it is recommended to skip this step): - <ul><li>xercesImpl-2.6.2.jar</li> -<li>xmlParserAPIs-2.6.2.jar</li> -</ul> -</p> + <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><TOMCAT_HOME>/conf/Catalina/localhost</code>: - <ul><li><PLUTO_SRCHOME>/pluto-portal/src/main/resources/pluto.xml</li> -<li><PLUTO_SRCHOME>/pluto-testsuite/src/main/resources/testsuite.xml</li> -</ul> -</p> + <ul><li><PLUTO_SRCHOME>/pluto-portal/src/main/resources/pluto.xml</li> +<li><PLUTO_SRCHOME>/pluto-testsuite/src/main/resources/testsuite.xml</li> +</ul> +</p> <p><b>Step 5:</b> Copy the following to <code><TOMCAT_HOME>/webapps</code>: - <ul><li><PLUTO_SRCHOME>/pluto-portal/target/pluto-portal.war</li> -<li><PLUTO_SRCHOME>/pluto-testsuite/target/pluto-testsuite.war</li> -</ul> -</p> -</div> -<div class="section"><h3><a name="Configuring_Source-Built_Pluto_for_Application_Scope_PortletSession_Attributes"></a>Configuring Source-Built Pluto for Application Scope PortletSession Attributes</h3> + <ul><li><PLUTO_SRCHOME>/pluto-portal/target/pluto-portal.war</li> +<li><PLUTO_SRCHOME>/pluto-testsuite/target/pluto-testsuite.war</li> +</ul> +</p> +</div> +<div class="section"><h3><a name="Configuring_Source-Built_Pluto_for_Application_Scope_PortletSession_Attributes"></a>Configuring Source-Built Pluto for Application Scope PortletSession Attributes</h3> <p>To be able to use application-scoped <code>PortletSession</code> attributes in Pluto, modify the Connector element for port 8080 in <code><TOMCAT_HOME>/conf/server.xml</code> by adding the following attribute and value: emptySessionPath="true". - </p> -</div> -<div class="section"><h3><a name="Configuring_User_and_Role_in_the_Pluto_Source_Build"></a>Configuring User and Role in the Pluto Source Build</h3> + </p> +</div> +<div class="section"><h3><a name="Configuring_User_and_Role_in_the_Pluto_Source_Build"></a>Configuring User and Role in the Pluto Source Build</h3> <p> The Pluto Testsuite portlet application needs the role '<code>pluto</code>' to run the Security Mapping Test. So before starting tomcat, you should @@ -430,11 +434,11 @@ $> mvn install <user username="both" password="tomcat" roles="tomcat,role1"/> <user username="pluto" password="pluto" roles="pluto,manager"/> </tomcat-users> - </pre> -</div> -</p> -</div> -<div class="section"><h3><a name="Starting_the_Portal"></a>Starting the Portal</h3> + </pre> +</div> +</p> +</div> +<div class="section"><h3><a name="Starting_the_Portal"></a>Starting the Portal</h3> <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 @@ -443,9 +447,9 @@ $> mvn install 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> -</div> -</div> + </p> +</div> +</div> </div> </div> @@ -454,7 +458,7 @@ $> mvn install </div> <div id="footer"> <div class="xright">© - 2004-2017 + 2004-2018 Apache Software Foundation Modified: portals/site-live/pluto/v11/release-notes.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v11/release-notes.html?rev=1834161&r1=1834160&r2=1834161&view=diff ============================================================================== --- portals/site-live/pluto/v11/release-notes.html (original) +++ portals/site-live/pluto/v11/release-notes.html Fri Jun 22 19:35:14 2018 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2017-01-13 + Last Published: 2018-06-22 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -105,6 +105,10 @@ </li> <li class="none"> + <a href="../security.html">Security</a> + </li> + + <li class="none"> <a href="../status.html">Status</a> </li> @@ -136,27 +140,27 @@ <ul> <li class="none"> - <a href="../v30/getting-started.html">Getting Started</a> + <a href="../v301/getting-started.html">Getting Started</a> </li> <li class="none"> - <a href="../v30/deploying.html">Deploying Portlets</a> + <a href="../v301/deploying.html">Deploying Portlets</a> </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet Concepts</a> + <a href="../v301/portlet-api.html">Portlet Concepts</a> </li> <li class="none"> - <a href="../v30/v3Features.html">Version 3 Features</a> + <a href="../v301/v3Features.html">Version 3 Features</a> </li> <li class="none"> - <a href="../v30/tck.html">Using the TCK</a> + <a href="../v301/tck.html">Using the TCK</a> </li> <li class="none"> - <a href="../v30/release-notes.html">Release Notes</a> + <a href="../v301/release-notes.html">Release Notes</a> </li> </ul> <h5>Pluto 2.0</h5> @@ -250,151 +254,151 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Pluto_1.1.7_Release_Notes"></a>Pluto 1.1.7 Release Notes</h2> -<div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-440"; class="externalLink">PLUTO-440</a> - portlet:actionURL not wrapping portlet:param</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-518"; class="externalLink">PLUTO-518</a> - DefineObjectsTag defines PortletRequest instead of RenderRequest</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-524"; class="externalLink">PLUTO-524</a> - Error in org.apache.pluto.core.DefaultUserInfoService</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-526"; class="externalLink">PLUTO-526</a> - portlet:param JSP tag doesn't handle multi-valued parameters</li> -</ul> -</div> -<div class="section"><h3><a name="Improvement"></a>Improvement</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-501"; class="externalLink">PLUTO-501</a> - Configuration errors are not much descriptive</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-503"; class="externalLink">PLUTO-503</a> - Expose createPortletScopedId and isInCurrentPortletScope of PortletSessionImpl as protected</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-504"; class="externalLink">PLUTO-504</a> - Create PortletSession via PortletEnvironmentService</li> -</ul> -</div> -</div> -<div class="section"><h2><a name="Pluto_1.1.6_Release_Notes"></a>Pluto 1.1.6 Release Notes</h2> -<div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-476"; class="externalLink">PLUTO-476</a> - Unused LocalStrings.properties with better messages</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-477"; class="externalLink">PLUTO-477</a> - PortletRequestImpl throws a NullPointerException when getting USER_INFO for unauthenticated users</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-484"; class="externalLink">PLUTO-484</a> - PortletURLImpl.setSecure() throws PortletSecurityException when PortletURLProvider.isSecureSupported() returns true</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-485"; class="externalLink">PLUTO-485</a> - Need to handle URIs that contain a question mark</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-490"; class="externalLink">PLUTO-490</a> - Cannot deploy portlets to ROOT context</li> -</ul> -</div> -<div class="section"><h3><a name="Improvement"></a>Improvement</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-486"; class="externalLink">PLUTO-486</a> - The USER_INFO map is re-created every time the USER_INFO attribute is retrieved using getAttribute() on org.apache.pluto.internal.impl.PortletRequestImpl</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-487"; class="externalLink">PLUTO-487</a> - PortletPreferencesImpl should not store the preferences every time it is instantiated</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-488"; class="externalLink">PLUTO-488</a> - When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-489"; class="externalLink">PLUTO-489</a> - Refactor request attribute handling into optional service interface</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-491"; class="externalLink">PLUTO-491</a> - Attach source jars to maven deployed artifacts</li> -</ul> -</div> -</div> -<div class="section"><h2><a name="Pluto_1.1.5_Release_Notes"></a>Pluto 1.1.5 Release Notes</h2> -<div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-356"; class="externalLink">PLUTO-356</a> - Pluto Driver not using injected Portal URL Parser</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-361"; class="externalLink">PLUTO-361</a> - Error when parsing the portal url</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-397"; class="externalLink">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"; class="externalLink">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"; class="externalLink">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"; class="externalLink">PLUTO-439</a> - Assembly code cannot parse Servlet 2.4 web.xml containing <jsp-config> tags</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-446"; class="externalLink">PLUTO-446</a> - No way to set default page encoding for Pluto</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-447"; class="externalLink">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"; class="externalLink">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"; class="externalLink">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"; class="externalLink">PLUTO-450</a> - ExternalAppScopedAttributeTest.jsp has a minor javascript error</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-451"; class="externalLink">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"; class="externalLink">PLUTO-452</a> - Assembler ant task fails on WAR with no manifest</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-455"; class="externalLink">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"; class="externalLink">PLUTO-457</a> - PortletContainerException doesn't chain Throwable</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-460"; class="externalLink">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"; class="externalLink">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"; class="externalLink">PLUTO-462</a> - isPortletModeAllowed and isWindowStateAllowed do case-sensitve checks</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-473"; class="externalLink">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"; class="externalLink">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"; class="externalLink">PLUTO-475</a> - Default Portlet Skin and WindowStateAnchorTag emit invalid markup</li> -</ul> -</div> -<div class="section"><h3><a name="Improvement"></a>Improvement</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-360"; class="externalLink">PLUTO-360</a> - FileAssemblerTest cannot be executed offline</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-394"; class="externalLink">PLUTO-394</a> - o.a.p.tags.el.ParamTag does not evaluate EL on "name" attribute</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-417"; class="externalLink">PLUTO-417</a> - PortletResponseImpl doesn't allow wsrp rewrite urls</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-456"; class="externalLink">PLUTO-456</a> - fix line endings on files.</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-458"; class="externalLink">PLUTO-458</a> - Improve exception handling with AbstractCastorDescriptorService</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-465"; class="externalLink">PLUTO-465</a> - Automatic determination of JAXP usage</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-472"; class="externalLink">PLUTO-472</a> - Fix Pluto Maven 2 release assemblies so they actually work.</li> -</ul> -</div> -</div> -<div class="section"><h2><a name="Pluto_1.1.4_Release_Notes"></a>Pluto 1.1.4 Release Notes</h2> -<div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-341"; class="externalLink">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"; class="externalLink">PLUTO-356</a> - Pluto Driver not using injected Portal URL Parser</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-361"; class="externalLink">PLUTO-361</a> - Error when parsing the portal url</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-369"; class="externalLink">PLUTO-369</a> - Inconsistency in PortletRequest attribute handling</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-370"; class="externalLink">PLUTO-370</a> - Cannot build 1.1.3 GA release from source</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-381"; class="externalLink">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"; class="externalLink">PLUTO-383</a> - DefaultUserInfo service returns null userinfo map</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-386"; class="externalLink">PLUTO-386</a> - Src distribution does not contain Pluto-AntTask.jar</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-389"; class="externalLink">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"; class="externalLink">PLUTO-390</a> - EarAssemblerTest failure</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-393"; class="externalLink">PLUTO-393</a> - Maximize Window State formatting problems in Firefox 2.0</li> -</ul> -</div> -<div class="section"><h3><a name="Improvement"></a>Improvement</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-347"; class="externalLink">PLUTO-347</a> - Remove dependency on shared/lib xerces and xmlAPIs</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-358"; class="externalLink">PLUTO-358</a> - Upgrade to Castor 1.1.1</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-375"; class="externalLink">PLUTO-375</a> - The ExpressionEvaluatorProxy for JSP 2.1 is unimplemented</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-376"; class="externalLink">PLUTO-376</a> - Update Pluto to work with Tomcat 6.x</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-384"; class="externalLink">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"; class="externalLink">PLUTO-385</a> - Use CSS-based tab navigation for Pluto Portal</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-387"; class="externalLink">PLUTO-387</a> - Provide add/remove page functionality to Pluto Portal Driver</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-388"; class="externalLink">PLUTO-388</a> - Removed use of deprecated method</li> -</ul> -</div> -<div class="section"><h3><a name="New_Feature"></a>New Feature</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-186"; class="externalLink">PLUTO-186</a> - ToolTips to Portlet Controls</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-359"; class="externalLink">PLUTO-359</a> - Add ability to assemble EAR files</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-382"; class="externalLink">PLUTO-382</a> - Have Page Administrator portlet persist new page configurations</li> -</ul> -</div> -</div> -<div class="section"><h2><a name="Pluto_1.1.3_Release_Notes"></a>Pluto 1.1.3 Release Notes</h2> -<div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-351"; class="externalLink">PLUTO-351</a> - Method removeAttribute in PortletRequestImpl causes NullPointerException in Resin 3.0.17 </li> -</ul> -</div> -<div class="section"><h3><a name="Improvement"></a>Improvement</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-350"; class="externalLink">PLUTO-350</a> - Remove absolute url dependency</li> -</ul> -</div> -<div class="section"><h3><a name="New_Feature"></a>New Feature</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-352"; class="externalLink">PLUTO-352</a> - Implement "Simple" Portlet Page Support</li> -</ul> -</div> -<div class="section"><h3><a name="Task"></a>Task</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-348"; class="externalLink">PLUTO-348</a> - Automate PGP key signing of M2 artifacts.</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-349"; class="externalLink">PLUTO-349</a> - Include META-INF/LICENSE and META-INF/NOTICE in maven artifacts</li> -</ul> -</div> -</div> -<div class="section"><h2><a name="Pluto_1.1.2_Release_Notes"></a>Pluto 1.1.2 Release Notes</h2> -<div class="section"><h3><a name="Bug"></a>Bug</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-331"; class="externalLink">PLUTO-331</a> - Page Admin Portlet fails in Pluto 1.1.1</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-332"; class="externalLink">PLUTO-332</a> - PortletContextManager.remove(InternalPortletContext) fails</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-336"; class="externalLink">PLUTO-336</a> - Provide alternate ways for deriving applicationId</li> -</ul> -</div> -<div class="section"><h3><a name="Improvement"></a>Improvement</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-334"; class="externalLink">PLUTO-334</a> - UserInfoService should provide PortletWindow in getUserInfo()</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-335"; class="externalLink">PLUTO-335</a> - Use proper namespacing for JavaScript in Page Admin Portlet</li> -<li><a href="https://issues.apache.org/jira/browse/PLUTO-338"; class="externalLink">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"; class="externalLink">PLUTO-344</a> - Update maven pluto plugin to accept a list of war files to assemble.</li> -</ul> -</div> -<div class="section"><h3><a name="New_Feature"></a>New Feature</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-328"; class="externalLink">PLUTO-328</a> - Add support for a callback right before Render and Action in PortletServlet</li> -</ul> -</div> -<div class="section"><h3><a name="Task"></a>Task</h3> -<ul><li><a href="https://issues.apache.org/jira/browse/PLUTO-339"; class="externalLink">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"; class="externalLink">PLUTO-345</a> - Fix link to distribution website on http://portals.apache.org/pluto/v11/getting-started.html</li> -</ul> -</div> -</div> + <div class="section"><h2><a name="Pluto_1.1.7_Release_Notes"></a>Pluto 1.1.7 Release Notes</h2> +<div class="section"><h3><a name="Bug"></a>Bug</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-440";>PLUTO-440</a> - portlet:actionURL not wrapping portlet:param</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-518";>PLUTO-518</a> - DefineObjectsTag defines PortletRequest instead of RenderRequest</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-524";>PLUTO-524</a> - Error in org.apache.pluto.core.DefaultUserInfoService</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-526";>PLUTO-526</a> - portlet:param JSP tag doesn't handle multi-valued parameters</li> +</ul> +</div> +<div class="section"><h3><a name="Improvement"></a>Improvement</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-501";>PLUTO-501</a> - Configuration errors are not much descriptive</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-503";>PLUTO-503</a> - Expose createPortletScopedId and isInCurrentPortletScope of PortletSessionImpl as protected</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-504";>PLUTO-504</a> - Create PortletSession via PortletEnvironmentService</li> +</ul> +</div> +</div> +<div class="section"><h2><a name="Pluto_1.1.6_Release_Notes"></a>Pluto 1.1.6 Release Notes</h2> +<div class="section"><h3><a name="Bug"></a>Bug</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-476";>PLUTO-476</a> - Unused LocalStrings.properties with better messages</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-477";>PLUTO-477</a> - PortletRequestImpl throws a NullPointerException when getting USER_INFO for unauthenticated users</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-484";>PLUTO-484</a> - PortletURLImpl.setSecure() throws PortletSecurityException when PortletURLProvider.isSecureSupported() returns true</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-485";>PLUTO-485</a> - Need to handle URIs that contain a question mark</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-490";>PLUTO-490</a> - Cannot deploy portlets to ROOT context</li> +</ul> +</div> +<div class="section"><h3><a name="Improvement"></a>Improvement</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-486";>PLUTO-486</a> - The USER_INFO map is re-created every time the USER_INFO attribute is retrieved using getAttribute() on org.apache.pluto.internal.impl.PortletRequestImpl</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-487";>PLUTO-487</a> - PortletPreferencesImpl should not store the preferences every time it is instantiated</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-488";>PLUTO-488</a> - When executing doAction/doRender/doLoad/doAdmin and retrieving the servlet context of the portlet app fails, a generic NullPointerException is thrown</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-489";>PLUTO-489</a> - Refactor request attribute handling into optional service interface</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-491";>PLUTO-491</a> - Attach source jars to maven deployed artifacts</li> +</ul> +</div> +</div> +<div class="section"><h2><a name="Pluto_1.1.5_Release_Notes"></a>Pluto 1.1.5 Release Notes</h2> +<div class="section"><h3><a name="Bug"></a>Bug</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-356";>PLUTO-356</a> - Pluto Driver not using injected Portal URL Parser</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-361";>PLUTO-361</a> - Error when parsing the portal url</li> +<li><a class="externalLink" 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 class="externalLink" 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 class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-439";>PLUTO-439</a> - Assembly code cannot parse Servlet 2.4 web.xml containing <jsp-config> tags</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-446";>PLUTO-446</a> - No way to set default page encoding for Pluto</li> +<li><a class="externalLink" 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 class="externalLink" 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 class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-450";>PLUTO-450</a> - ExternalAppScopedAttributeTest.jsp has a minor javascript error</li> +<li><a class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-452";>PLUTO-452</a> - Assembler ant task fails on WAR with no manifest</li> +<li><a class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-457";>PLUTO-457</a> - PortletContainerException doesn't chain Throwable</li> +<li><a class="externalLink" 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 class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-462";>PLUTO-462</a> - isPortletModeAllowed and isWindowStateAllowed do case-sensitve checks</li> +<li><a class="externalLink" 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 class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-475";>PLUTO-475</a> - Default Portlet Skin and WindowStateAnchorTag emit invalid markup</li> +</ul> +</div> +<div class="section"><h3><a name="Improvement"></a>Improvement</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-360";>PLUTO-360</a> - FileAssemblerTest cannot be executed offline</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-394";>PLUTO-394</a> - o.a.p.tags.el.ParamTag does not evaluate EL on "name" attribute</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-417";>PLUTO-417</a> - PortletResponseImpl doesn't allow wsrp rewrite urls</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-456";>PLUTO-456</a> - fix line endings on files.</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-458";>PLUTO-458</a> - Improve exception handling with AbstractCastorDescriptorService</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-465";>PLUTO-465</a> - Automatic determination of JAXP usage</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-472";>PLUTO-472</a> - Fix Pluto Maven 2 release assemblies so they actually work.</li> +</ul> +</div> +</div> +<div class="section"><h2><a name="Pluto_1.1.4_Release_Notes"></a>Pluto 1.1.4 Release Notes</h2> +<div class="section"><h3><a name="Bug"></a>Bug</h3> +<ul><li><a class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-356";>PLUTO-356</a> - Pluto Driver not using injected Portal URL Parser</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-361";>PLUTO-361</a> - Error when parsing the portal url</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-369";>PLUTO-369</a> - Inconsistency in PortletRequest attribute handling</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-370";>PLUTO-370</a> - Cannot build 1.1.3 GA release from source</li> +<li><a class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-383";>PLUTO-383</a> - DefaultUserInfo service returns null userinfo map</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-386";>PLUTO-386</a> - Src distribution does not contain Pluto-AntTask.jar</li> +<li><a class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-390";>PLUTO-390</a> - EarAssemblerTest failure</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-393";>PLUTO-393</a> - Maximize Window State formatting problems in Firefox 2.0</li> +</ul> +</div> +<div class="section"><h3><a name="Improvement"></a>Improvement</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-347";>PLUTO-347</a> - Remove dependency on shared/lib xerces and xmlAPIs</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-358";>PLUTO-358</a> - Upgrade to Castor 1.1.1</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-375";>PLUTO-375</a> - The ExpressionEvaluatorProxy for JSP 2.1 is unimplemented</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-376";>PLUTO-376</a> - Update Pluto to work with Tomcat 6.x</li> +<li><a class="externalLink" 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 class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-385";>PLUTO-385</a> - Use CSS-based tab navigation for Pluto Portal</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-387";>PLUTO-387</a> - Provide add/remove page functionality to Pluto Portal Driver</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-388";>PLUTO-388</a> - Removed use of deprecated method</li> +</ul> +</div> +<div class="section"><h3><a name="New_Feature"></a>New Feature</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-186";>PLUTO-186</a> - ToolTips to Portlet Controls</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-359";>PLUTO-359</a> - Add ability to assemble EAR files</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-382";>PLUTO-382</a> - Have Page Administrator portlet persist new page configurations</li> +</ul> +</div> +</div> +<div class="section"><h2><a name="Pluto_1.1.3_Release_Notes"></a>Pluto 1.1.3 Release Notes</h2> +<div class="section"><h3><a name="Bug"></a>Bug</h3> +<ul><li><a class="externalLink" 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> +</div> +<div class="section"><h3><a name="Improvement"></a>Improvement</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-350";>PLUTO-350</a> - Remove absolute url dependency</li> +</ul> +</div> +<div class="section"><h3><a name="New_Feature"></a>New Feature</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-352";>PLUTO-352</a> - Implement "Simple" Portlet Page Support</li> +</ul> +</div> +<div class="section"><h3><a name="Task"></a>Task</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-348";>PLUTO-348</a> - Automate PGP key signing of M2 artifacts.</li> +<li><a class="externalLink" 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> +</div> +</div> +<div class="section"><h2><a name="Pluto_1.1.2_Release_Notes"></a>Pluto 1.1.2 Release Notes</h2> +<div class="section"><h3><a name="Bug"></a>Bug</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-331";>PLUTO-331</a> - Page Admin Portlet fails in Pluto 1.1.1</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-332";>PLUTO-332</a> - PortletContextManager.remove(InternalPortletContext) fails</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-336";>PLUTO-336</a> - Provide alternate ways for deriving applicationId</li> +</ul> +</div> +<div class="section"><h3><a name="Improvement"></a>Improvement</h3> +<ul><li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-334";>PLUTO-334</a> - UserInfoService should provide PortletWindow in getUserInfo()</li> +<li><a class="externalLink" href="https://issues.apache.org/jira/browse/PLUTO-335";>PLUTO-335</a> - Use proper namespacing for JavaScript in Page Admin Portlet</li> +<li><a class="externalLink" 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 class="externalLink" 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> +</div> +<div class="section"><h3><a name="New_Feature"></a>New Feature</h3> +<ul><li><a class="externalLink" 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> +</div> +<div class="section"><h3><a name="Task"></a>Task</h3> +<ul><li><a class="externalLink" 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 class="externalLink" 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> +</div> +</div> </div> </div> @@ -403,7 +407,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2017 + 2004-2018 Apache Software Foundation Modified: portals/site-live/pluto/v20/app-servers.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v20/app-servers.html?rev=1834161&r1=1834160&r2=1834161&view=diff ============================================================================== --- portals/site-live/pluto/v20/app-servers.html (original) +++ portals/site-live/pluto/v20/app-servers.html Fri Jun 22 19:35:14 2018 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2017-01-13 + Last Published: 2018-06-22 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -105,6 +105,10 @@ </li> <li class="none"> + <a href="../security.html">Security</a> + </li> + + <li class="none"> <a href="../status.html">Status</a> </li> @@ -136,27 +140,27 @@ <ul> <li class="none"> - <a href="../v30/getting-started.html">Getting Started</a> + <a href="../v301/getting-started.html">Getting Started</a> </li> <li class="none"> - <a href="../v30/deploying.html">Deploying Portlets</a> + <a href="../v301/deploying.html">Deploying Portlets</a> </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet Concepts</a> + <a href="../v301/portlet-api.html">Portlet Concepts</a> </li> <li class="none"> - <a href="../v30/v3Features.html">Version 3 Features</a> + <a href="../v301/v3Features.html">Version 3 Features</a> </li> <li class="none"> - <a href="../v30/tck.html">Using the TCK</a> + <a href="../v301/tck.html">Using the TCK</a> </li> <li class="none"> - <a href="../v30/release-notes.html">Release Notes</a> + <a href="../v301/release-notes.html">Release Notes</a> </li> </ul> <h5>Pluto 2.0</h5> @@ -250,32 +254,32 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Supported_Application_Servers"></a>Supported Application Servers</h2> -<p>The following application servers have been tested with Pluto 2.0.3:</p> -<p><table class="bodyTable"><tr class="a"><th>App Server</th> -<th>Version</th> -<th>Status</th> -<th>Notes</th> -</tr> -<tr class="b"><td>Tomcat</td> -<td>6.0.33</td> -<td>WORKING</td> + <div class="section"><h2><a name="Supported_Application_Servers"></a>Supported Application Servers</h2> +<p>The following application servers have been tested with Pluto 2.0.3:</p> +<p><table class="bodyTable"><tr class="a"><th>App Server</th> +<th>Version</th> +<th>Status</th> +<th>Notes</th> +</tr> +<tr class="b"><td>Tomcat</td> +<td>6.0.33</td> +<td>WORKING</td> <td> Use <code>mvn pluto2:install -DinstallDir=/path/to/tomcat</code> to install the container and portal into Tomcat. - </td> -</tr> -<tr class="a"><td>Tomcat</td> -<td>7.0.21</td> -<td>WORKING</td> + </td> +</tr> +<tr class="a"><td>Tomcat</td> +<td>7.0.21</td> +<td>WORKING</td> <td> Use <code>mvn pluto2:install -DinstallDir=/path/to/tomcat</code> to install the container and portal into Tomcat. - </td> -</tr> -</table> -</p> -</div> + </td> +</tr> +</table> +</p> +</div> </div> </div> @@ -284,7 +288,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2017 + 2004-2018 Apache Software Foundation Modified: portals/site-live/pluto/v20/deploying.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v20/deploying.html?rev=1834161&r1=1834160&r2=1834161&view=diff ============================================================================== --- portals/site-live/pluto/v20/deploying.html (original) +++ portals/site-live/pluto/v20/deploying.html Fri Jun 22 19:35:14 2018 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2017-01-13 + Last Published: 2018-06-22 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -105,6 +105,10 @@ </li> <li class="none"> + <a href="../security.html">Security</a> + </li> + + <li class="none"> <a href="../status.html">Status</a> </li> @@ -136,27 +140,27 @@ <ul> <li class="none"> - <a href="../v30/getting-started.html">Getting Started</a> + <a href="../v301/getting-started.html">Getting Started</a> </li> <li class="none"> - <a href="../v30/deploying.html">Deploying Portlets</a> + <a href="../v301/deploying.html">Deploying Portlets</a> </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet Concepts</a> + <a href="../v301/portlet-api.html">Portlet Concepts</a> </li> <li class="none"> - <a href="../v30/v3Features.html">Version 3 Features</a> + <a href="../v301/v3Features.html">Version 3 Features</a> </li> <li class="none"> - <a href="../v30/tck.html">Using the TCK</a> + <a href="../v301/tck.html">Using the TCK</a> </li> <li class="none"> - <a href="../v30/release-notes.html">Release Notes</a> + <a href="../v301/release-notes.html">Release Notes</a> </li> </ul> <h5>Pluto 2.0</h5> @@ -250,7 +254,7 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Deploying_Portlet_to_Pluto_Portal"></a>Deploying Portlet to Pluto Portal</h2> + <div class="section"><h2><a name="Deploying_Portlet_to_Pluto_Portal"></a>Deploying Portlet to Pluto Portal</h2> <p> There are 2 steps involved in deploying a portlet application in Pluto 2.0: <ul><li><b>Assembly</b>: All portlet applications must be run through the @@ -259,28 +263,28 @@ and servlet mapping are added to the deployment descriptor (web.xml). This servlet <code>org.apache.pluto.container.driver.PortletServlet</code> will be used to dispatch portlet requests to the portlet application. - </li> + </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 7.0.21 as the servlet engine. - </li> -</ul> -</p> -<div class="section"><h3><a name="Portlet_Assembly"></a>Portlet Assembly</h3> + </li> +</ul> +</p> +<div class="section"><h3><a name="Portlet_Assembly"></a>Portlet Assembly</h3> <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> <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> <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> <p><div class="source"><pre> HelloWorldPortlet (top level directory) |- pom.xml (the pom file) @@ -300,18 +304,18 @@ `- WEB-INF `- portlet.xml (JSR-168 deployment descriptor) `- web.xml (This will be modified by maven-pluto-plugin) - </pre> -</div> -</p> + </pre> +</div> +</p> <p> This is an example of what the Tomcat context deployment descriptor will contain: <div class="source"><pre> <Context path="/HelloWorldPortlet" docBase="HelloWorldPortlet" crossContext="true"/> - </pre> -</div> -</p> + </pre> +</div> +</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 @@ -402,15 +406,15 @@ </build> </project> - </pre> -</div> -</p> + </pre> +</div> +</p> <p> Once configured, the war generated by an 'mvn package' (or install) command will contain the appropriate pluto configuration. - </p> -</div> -<div class="section"><h3><a name="Portlet_Deployment"></a>Portlet Deployment</h3> + </p> +</div> +<div class="section"><h3><a name="Portlet_Deployment"></a>Portlet Deployment</h3> <p> To deploy a portlet application, simply deploy the application war using any standard mechanism for your application server. There are many @@ -418,12 +422,12 @@ 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> <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> + </p> <div class="source"><pre> <plugin> <artifactId>maven-antrun-plugin</artifactId> @@ -444,30 +448,30 @@ </execution> </executions> </plugin> - </pre> -</div> + </pre> +</div> <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> -</div> -<div class="section"><h3><a name="Portlet_Publishing"></a>Portlet Publishing</h3> + </p> +</div> +<div class="section"><h3><a name="Portlet_Publishing"></a>Portlet Publishing</h3> <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> +<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> <p> The page can then be configured by adding a <code>page</code> child element of the <code>render-config</code> element, like this: @@ -481,18 +485,18 @@ name="your_portlet_2"/> </page> </render-config> - </pre> -</div> -</p> + </pre> +</div> +</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> -</div> -</div> + </p> +</div> +</div> </div> </div> @@ -501,7 +505,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2017 + 2004-2018 Apache Software Foundation Modified: portals/site-live/pluto/v20/embedding.html URL: http://svn.apache.org/viewvc/portals/site-live/pluto/v20/embedding.html?rev=1834161&r1=1834160&r2=1834161&view=diff ============================================================================== --- portals/site-live/pluto/v20/embedding.html (original) +++ portals/site-live/pluto/v20/embedding.html Fri Jun 22 19:35:14 2018 @@ -47,7 +47,7 @@ <div class="xleft"> - Last Published: 2017-01-13 + Last Published: 2018-06-22 | <a href="http://portals.apache.org/pluto"; class="externalLink">Home</a> </div> @@ -105,6 +105,10 @@ </li> <li class="none"> + <a href="../security.html">Security</a> + </li> + + <li class="none"> <a href="../status.html">Status</a> </li> @@ -136,27 +140,27 @@ <ul> <li class="none"> - <a href="../v30/getting-started.html">Getting Started</a> + <a href="../v301/getting-started.html">Getting Started</a> </li> <li class="none"> - <a href="../v30/deploying.html">Deploying Portlets</a> + <a href="../v301/deploying.html">Deploying Portlets</a> </li> <li class="none"> - <a href="../v30/portlet-api.html">Portlet Concepts</a> + <a href="../v301/portlet-api.html">Portlet Concepts</a> </li> <li class="none"> - <a href="../v30/v3Features.html">Version 3 Features</a> + <a href="../v301/v3Features.html">Version 3 Features</a> </li> <li class="none"> - <a href="../v30/tck.html">Using the TCK</a> + <a href="../v301/tck.html">Using the TCK</a> </li> <li class="none"> - <a href="../v30/release-notes.html">Release Notes</a> + <a href="../v301/release-notes.html">Release Notes</a> </li> </ul> <h5>Pluto 2.0</h5> @@ -250,30 +254,30 @@ </div> <div id="bodyColumn"> <div id="contentBox"> - <div class="section"><h2><a name="Embedding_the_Pluto_2.0_Container"></a>Embedding the Pluto 2.0 Container</h2> + <div class="section"><h2><a name="Embedding_the_Pluto_2.0_Container"></a>Embedding the Pluto 2.0 Container</h2> <p> When not using the Pluto Driver, and when you want to embed the Pluto container in your portal or development environment, you will need the following jar files... - </p> + </p> <p> Copy the following files to <code><TOMCAT_HOME>/lib on Tomcat 6+</code>: - <ul><li>portlet-api_2.0_spec-1.0.jar</li> -<li>ccpp-1.0.jar</li> -<li>pluto-container-api-2.0.3.jar</li> -<li>pluto-container-driver-api-2.0.3.jar</li> -<li>pluto-taglib-2.0.3.jar</li> -<li>portlet-api_2.0_spec-1.0.jar</li> -</ul> -</p> + <ul><li>portlet-api_2.0_spec-1.0.jar</li> +<li>ccpp-1.0.jar</li> +<li>pluto-container-api-2.0.3.jar</li> +<li>pluto-container-driver-api-2.0.3.jar</li> +<li>pluto-taglib-2.0.3.jar</li> +<li>portlet-api_2.0_spec-1.0.jar</li> +</ul> +</p> <p><b>Implementation:</b> Copy into your portal implementation such as WEB-INF/lib: - <ul><li>jaxb-api-2.1.jar</li> -<li>jaxb-impl-2.1.0.jar</li> -<li>pluto-container-2.0.3.jar</li> -<li>stax-api-1.0.2.jar</li> -<li>stax-1.2.0.jar</li> -</ul> -</p> -</div> + <ul><li>jaxb-api-2.1.jar</li> +<li>jaxb-impl-2.1.0.jar</li> +<li>pluto-container-2.0.3.jar</li> +<li>stax-api-1.0.2.jar</li> +<li>stax-1.2.0.jar</li> +</ul> +</p> +</div> </div> </div> @@ -282,7 +286,7 @@ </div> <div id="footer"> <div class="xright">© - 2004-2017 + 2004-2018 Apache Software Foundation
