You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-scm@portals.apache.org by es...@apache.org on 2007/03/04 02:36:46 UTC
svn commit: r514318 - in /portals/pluto/trunk/pluto-site/src/site/xdoc/v11:
app-servers.xml architecture.xml deploying.xml getting-started.xml
resources.xml subprojects.xml
Author: esm
Date: Sat Mar 3 17:36:45 2007
New Revision: 514318
URL: http://svn.apache.org/viewvc?view=rev&rev=514318
Log:
Updating line endings only.
Modified:
portals/pluto/trunk/pluto-site/src/site/xdoc/v11/app-servers.xml (contents, props changed)
portals/pluto/trunk/pluto-site/src/site/xdoc/v11/architecture.xml (props changed)
portals/pluto/trunk/pluto-site/src/site/xdoc/v11/deploying.xml (contents, props changed)
portals/pluto/trunk/pluto-site/src/site/xdoc/v11/getting-started.xml (contents, props changed)
portals/pluto/trunk/pluto-site/src/site/xdoc/v11/resources.xml (contents, props changed)
portals/pluto/trunk/pluto-site/src/site/xdoc/v11/subprojects.xml (contents, props changed)
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/v11/app-servers.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/v11/app-servers.xml?view=diff&rev=514318&r1=514317&r2=514318
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/v11/app-servers.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/v11/app-servers.xml Sat Mar 3 17:36:45 2007
@@ -1,96 +1,96 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
+<?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>
- <author email="ddewolf@apache.org">David DeWolf</author>
- </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.
- </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>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>
-
+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>
+ <author email="ddewolf@apache.org">David DeWolf</author>
+ </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.
+ </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>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/pluto-site/src/site/xdoc/v11/app-servers.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/pluto/trunk/pluto-site/src/site/xdoc/v11/architecture.xml
------------------------------------------------------------------------------
svn:eol-style = native
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/v11/deploying.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/v11/deploying.xml?view=diff&rev=514318&r1=514317&r2=514318
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/v11/deploying.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/v11/deploying.xml Sat Mar 3 17:36:45 2007
@@ -1,263 +1,263 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
+<?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>
- <author email="zheng.at.apache.D0T.org">ZHENG Zhong</author>
- <author email="ddewolf@apache.org">David DeWolf</author>
- <author email="cdoremus@apache.org">Craig Doremus</author>
- </properties>
-
- <body>
-
- <section name="Deploying Portlet to Pluto Portal">
-
- <p>
- There are 2 involved in deploying a portlet application Pluto 1.1:
- <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 binary 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 also deploys
- 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)
- |- resources
- | `- HelloWorldPortlet.xml (Tomcat context deployment descriptor)
- |- webapp (webapp resources (jsp, css, images) go under here)
- `- jsp
- `- HelloWorldPortletView.jsp (for view mode)
- `- HelloWorldPortletEdit.jsp (for edit mode)
- `- 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="../PlutoDomain/HelloWorldPortlet.war"
- 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 for a new Pluto version -->
- <pluto.version>1.1.0</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 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 'process-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) 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
- a manager web console. This console is pointed to the Tomcat manager webapp in the
- Pluto binary 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>
- </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 portlet application should be first configured in pluto-portal-driver-config.xml by
- adding a <code>portlet-app</code> element with appropriate child elements like this:
- <source>
-<portlet-app>
- <context-path>/your_portlet_app_context_path</context-path>
- <portlets>
- <portlet name="your_portlet_1"/>
- <portlet name="your_portlet_2"/>
- </portlets>
-</portlet-app>
- </source>
- </p>
- <p>
- The page can then be configured by adding a <code>page</code> element in 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>
- <p>
- The value of the <code>context-path element</code> within the <code>portlet-app</code> record must correspond to the
- value of the <code>context</code> attribute in the <code>portlet</code> element. In addition, the value of the
- <code>name</code> attribute in the <code>portlet</code> child element of <code>portlet-app</code> must correspond to
- the value of the <code>name</code> attribute of the <code>portlet</code> child element of page.
- </p>
- </subsection>
-
- </section>
-
- </body>
-
-</document>
-
+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>
+ <author email="zheng.at.apache.D0T.org">ZHENG Zhong</author>
+ <author email="ddewolf@apache.org">David DeWolf</author>
+ <author email="cdoremus@apache.org">Craig Doremus</author>
+ </properties>
+
+ <body>
+
+ <section name="Deploying Portlet to Pluto Portal">
+
+ <p>
+ There are 2 involved in deploying a portlet application Pluto 1.1:
+ <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 binary 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 also deploys
+ 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)
+ |- resources
+ | `- HelloWorldPortlet.xml (Tomcat context deployment descriptor)
+ |- webapp (webapp resources (jsp, css, images) go under here)
+ `- jsp
+ `- HelloWorldPortletView.jsp (for view mode)
+ `- HelloWorldPortletEdit.jsp (for edit mode)
+ `- 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="../PlutoDomain/HelloWorldPortlet.war"
+ 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 for a new Pluto version -->
+ <pluto.version>1.1.0</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 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 'process-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) 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
+ a manager web console. This console is pointed to the Tomcat manager webapp in the
+ Pluto binary 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>
+ </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 portlet application should be first configured in pluto-portal-driver-config.xml by
+ adding a <code>portlet-app</code> element with appropriate child elements like this:
+ <source>
+<portlet-app>
+ <context-path>/your_portlet_app_context_path</context-path>
+ <portlets>
+ <portlet name="your_portlet_1"/>
+ <portlet name="your_portlet_2"/>
+ </portlets>
+</portlet-app>
+ </source>
+ </p>
+ <p>
+ The page can then be configured by adding a <code>page</code> element in 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>
+ <p>
+ The value of the <code>context-path element</code> within the <code>portlet-app</code> record must correspond to the
+ value of the <code>context</code> attribute in the <code>portlet</code> element. In addition, the value of the
+ <code>name</code> attribute in the <code>portlet</code> child element of <code>portlet-app</code> must correspond to
+ the value of the <code>name</code> attribute of the <code>portlet</code> child element of page.
+ </p>
+ </subsection>
+
+ </section>
+
+ </body>
+
+</document>
+
Propchange: portals/pluto/trunk/pluto-site/src/site/xdoc/v11/deploying.xml
------------------------------------------------------------------------------
svn:eol-style = native
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/v11/getting-started.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/v11/getting-started.xml?view=diff&rev=514318&r1=514317&r2=514318
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/v11/getting-started.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/v11/getting-started.xml Sat Mar 3 17:36:45 2007
@@ -1,106 +1,106 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
+<?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>
- <author email="ddewolf@apache.org">David DeWolf</author>
- <author email="zheng.at.apache.D0T.org">ZHENG Zhong</author>
- <author email="cdoremus@apache.org">Craig Doremus</author>
- </properties>
-
- <body>
-
- <section name="Installing the Pluto 1.1 Binary Build">
-
- <ol>
- <li>Download a Pluto 1.1 binary distribution from
- a <a href="http://cvs.apache.org/dist/portals/pluto/">distribution site</a>.</li>
- <li>Unzip the binary distribution into a directory.</li>
- <ol>
- <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>
- <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 the user pluto (password=pluto).</li>
- </ol>
-
- </section>
-
- <section name="Building Pluto from Source">
-
- <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>
-
- <subsection name="Obtaining Pluto 1.1 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 1.1 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 1.1 (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.0 source to the 'pluto' directory use this command:
- <pre>svn checkout https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0 pluto</pre>
- </p>
-
- <p>
- Zipped up Pluto 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">
+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>
+ <author email="ddewolf@apache.org">David DeWolf</author>
+ <author email="zheng.at.apache.D0T.org">ZHENG Zhong</author>
+ <author email="cdoremus@apache.org">Craig Doremus</author>
+ </properties>
+
+ <body>
+
+ <section name="Installing the Pluto 1.1 Binary Build">
+
+ <ol>
+ <li>Download a Pluto 1.1 binary distribution from
+ a <a href="http://cvs.apache.org/dist/portals/pluto/">distribution site</a>.</li>
+ <li>Unzip the binary distribution into a directory.</li>
+ <ol>
+ <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>
+ <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 the user pluto (password=pluto).</li>
+ </ol>
+
+ </section>
+
+ <section name="Building Pluto from Source">
+
+ <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>
+
+ <subsection name="Obtaining Pluto 1.1 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 1.1 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 1.1 (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.0 source to the 'pluto' directory use this command:
+ <pre>svn checkout https://svn.apache.org/repos/asf/portals/pluto/tags/pluto-1.1.0 pluto</pre>
+ </p>
+
+ <p>
+ Zipped up Pluto 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 <pluginGroups> element:
@@ -118,143 +118,143 @@
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>
- <code><PLUTO-1.1-SRCHOME></code> is the local directory where the
- Pluto 1.1 source distribution has been checked out or unzipped into.
- </p>
- <p>
- <source><![CDATA[
-$> cd <PLUTO-1.1-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 1.1 install has been tested on Tomcat 5.5.9, 5.5.17 and 5.5.20.
- 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 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-1.1-SRCHOME></code>.
- </p>
- <p>
- <b>Step 1:</b>
- <source><![CDATA[
-$> cd <PLUTO-1.1-SRCHOME>
-$> mvn install
- ]]></source>
- </p>
- <p>
- <b>Step 2:</b> Copy the following to
- <code><TOMCAT_HOME>/shared/lib</code>:
- <ul>
- <li>castor-1.0.jar</li>
- <li>portlet-api-1.0.jar</li>
- <li>pluto-container-1.1.0.jar</li>
- <li>pluto-descriptor-api-1.1.0.jar</li>
- <li>pluto-descriptor-impl-1.1.0.jar</li>
- <li>pluto-taglib-1.1.0.jar</li>
- </ul>
- </p>
- <p>
- <b>Step 3:</b> Copy the following to
- <code><TOMCAT_HOME>/common/endorsed</code>:
- <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>
- <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>
- </subsection>
-
- <subsection name="Installing Pluto with a Windows EXE">
- <p>
- The NSIS Installer is not yet complete, but we hope to have a fully
- functional one soon. Anyone is more than welcome to assist us in
- this process.
- </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><TOMCAT_HOME>/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><TOMCAT_HOME>/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="pluto"/>
- <role rolename="tomcat"/>
- <role rolename="role1"/>
- <user username="tomcat" password="tomcat" roles="tomcat,pluto"/>
- <user username="role1" password="tomcat" roles="role1"/>
- <user username="both" password="tomcat" roles="tomcat,role1"/>
-</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><TOMCAT_HOME>/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>
-
+ <p>
+ <code><PLUTO-1.1-SRCHOME></code> is the local directory where the
+ Pluto 1.1 source distribution has been checked out or unzipped into.
+ </p>
+ <p>
+ <source><![CDATA[
+$> cd <PLUTO-1.1-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 1.1 install has been tested on Tomcat 5.5.9, 5.5.17 and 5.5.20.
+ 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 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-1.1-SRCHOME></code>.
+ </p>
+ <p>
+ <b>Step 1:</b>
+ <source><![CDATA[
+$> cd <PLUTO-1.1-SRCHOME>
+$> mvn install
+ ]]></source>
+ </p>
+ <p>
+ <b>Step 2:</b> Copy the following to
+ <code><TOMCAT_HOME>/shared/lib</code>:
+ <ul>
+ <li>castor-1.0.jar</li>
+ <li>portlet-api-1.0.jar</li>
+ <li>pluto-container-1.1.0.jar</li>
+ <li>pluto-descriptor-api-1.1.0.jar</li>
+ <li>pluto-descriptor-impl-1.1.0.jar</li>
+ <li>pluto-taglib-1.1.0.jar</li>
+ </ul>
+ </p>
+ <p>
+ <b>Step 3:</b> Copy the following to
+ <code><TOMCAT_HOME>/common/endorsed</code>:
+ <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>
+ <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>
+ </subsection>
+
+ <subsection name="Installing Pluto with a Windows EXE">
+ <p>
+ The NSIS Installer is not yet complete, but we hope to have a fully
+ functional one soon. Anyone is more than welcome to assist us in
+ this process.
+ </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><TOMCAT_HOME>/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><TOMCAT_HOME>/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="pluto"/>
+ <role rolename="tomcat"/>
+ <role rolename="role1"/>
+ <user username="tomcat" password="tomcat" roles="tomcat,pluto"/>
+ <user username="role1" password="tomcat" roles="role1"/>
+ <user username="both" password="tomcat" roles="tomcat,role1"/>
+</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><TOMCAT_HOME>/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/pluto-site/src/site/xdoc/v11/getting-started.xml
------------------------------------------------------------------------------
svn:eol-style = native
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/v11/resources.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/v11/resources.xml?view=diff&rev=514318&r1=514317&r2=514318
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/v11/resources.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/v11/resources.xml Sat Mar 3 17:36:45 2007
@@ -1,75 +1,75 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
+<?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 and Portlet Resources</title>
- <author email="ddewolf@apache.org">David DeWolf</author>
- </properties>
-
- <body>
-
- <section name="The Java Portlet Specifications">
- <p>
- <ul>
- <li><a href="http://jcp.org/en/jsr/detail?id=168">JSR-168: Portlet Specification 1.0</a></li>
- <li><a href="http://jcp.org/en/jsr/detail?id=286">JSR-286: Portlet Specification 2.0</a></li>
- </ul>
- </p>
- </section>
-
- <section name="Additional Pluto Documentation">
- <p>
- <ul>
- <li>
- <a href="http://wiki.apache.org/portals/Pluto">Official Pluto Wiki</a>
- </li>
- <li>
- <a href="http://people.apache.org/~zheng/pluto/chinese/">Pluto
- Website, Chinese Translation</a> maintained by ZHENG Zhong
- </li>
- </ul>
- </p>
- </section>
-
- <section name="Articles, Whitepapers, and Presentations">
- <p>
- <ul>
- <li>
- <a href="http://www.developer.com/java/web/article.php/3547186">Introduction to the Portlet Specification</a>
- by David H. DeWolf, September 2005
- </li>
- <li>
- <a href="http://www.developer.com/java/web/article.php/3554396">Developing Portlets with Apache Pluto 1.1</a>
- by David H. DeWolf, October 2005
- </li>
- <li>
- <a href="http://www.developer.com/java/web/article.php/3563411">Embedding Apache Pluto 1.1</a>
- by David H. DeWolf, September 2005
- </li>
- </ul>
- </p>
- </section>
-
- </body>
-
-</document>
-
+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 and Portlet Resources</title>
+ <author email="ddewolf@apache.org">David DeWolf</author>
+ </properties>
+
+ <body>
+
+ <section name="The Java Portlet Specifications">
+ <p>
+ <ul>
+ <li><a href="http://jcp.org/en/jsr/detail?id=168">JSR-168: Portlet Specification 1.0</a></li>
+ <li><a href="http://jcp.org/en/jsr/detail?id=286">JSR-286: Portlet Specification 2.0</a></li>
+ </ul>
+ </p>
+ </section>
+
+ <section name="Additional Pluto Documentation">
+ <p>
+ <ul>
+ <li>
+ <a href="http://wiki.apache.org/portals/Pluto">Official Pluto Wiki</a>
+ </li>
+ <li>
+ <a href="http://people.apache.org/~zheng/pluto/chinese/">Pluto
+ Website, Chinese Translation</a> maintained by ZHENG Zhong
+ </li>
+ </ul>
+ </p>
+ </section>
+
+ <section name="Articles, Whitepapers, and Presentations">
+ <p>
+ <ul>
+ <li>
+ <a href="http://www.developer.com/java/web/article.php/3547186">Introduction to the Portlet Specification</a>
+ by David H. DeWolf, September 2005
+ </li>
+ <li>
+ <a href="http://www.developer.com/java/web/article.php/3554396">Developing Portlets with Apache Pluto 1.1</a>
+ by David H. DeWolf, October 2005
+ </li>
+ <li>
+ <a href="http://www.developer.com/java/web/article.php/3563411">Embedding Apache Pluto 1.1</a>
+ by David H. DeWolf, September 2005
+ </li>
+ </ul>
+ </p>
+ </section>
+
+ </body>
+
+</document>
+
Propchange: portals/pluto/trunk/pluto-site/src/site/xdoc/v11/resources.xml
------------------------------------------------------------------------------
svn:eol-style = native
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/v11/subprojects.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/v11/subprojects.xml?view=diff&rev=514318&r1=514317&r2=514318
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/v11/subprojects.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/v11/subprojects.xml Sat Mar 3 17:36:45 2007
@@ -1,138 +1,138 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
+<?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 Subprojects</title>
- <author email="ddewolf@apache.org">David DeWolf</author>
- </properties>
-
- <body>
- <section name="Pluto Subprojects">
-
- <p>
- Pluto 1.1 utilizes Maven 2 as it's project management and build
- automation tool. Pluto follows maven's best practices and is organized
- into modules or subprojects.
- </p>
-
- <subsection name="Container Subprojects">
- <p>
- <ul>
- <li>
- <b>Pluto Container:</b>
- The Pluto Container is the core compontent of the Apache Pluto
- project. All other modules either support the development. The
- Pluto Container is the reference implementation of the Portlet
- Specification.
- </li>
- <li>
- <b>Pluto Tags:</b>
- The Java Portlet Tag Library implementation which is provided
- with the container.
- </li>
- </ul>
- </p>
- </subsection>
-
- <subsection name="Portal/Testing Subprojects">
- <p>
- <ul>
- <li>
- <b>Pluto Portal Driver:</b>
- A driver library for the Pluto Portlet Container. Provides service
- implementations and utilities for implementing a portal which
- utilizes the container.
- </li>
- <li>
- <b>Pluto Portal:</b>
- The user interface components (web application) of the Pluto
- Portal. The pluto portal is a simple portal application which
- embeds the portal. The portal is not meant to be a full enterprise
- portal, but instead is meant to be an example of how to embed the
- container and a lightweight environment for developing and testing
- portlets.
- </li>
- <li>
- <b>Pluto Testsuite:</b>
- A test portlet which can be used to exercise and test any portlet
- container.
- </li>
- </ul>
- </p>
- </subsection>
-
- <subsection name="Libraries and Supporting Subprojects">
- <p>
- <ul>
- <li>
- <b>Pluto Descriptor API:</b>
- A domain model which represents the deployment descriptors read
- by the portlet container. Contains service interfaces for reading
- and writing portlet.xml and web.xml.
- </li>
- <li>
- <b>Pluto Descriptor Impl:</b>
- The default implementation of the Pluto Descriptor API Subproject.
- The default implementation utilzes castor for reading and writing
- portlet and web application descriptors.
- </li>
- <li>
- <b>Pluto Optional Services:</b>
- Provides optional implementations of the Pluto Container Services.
- Includes database implementations of the PortletPreferencesService
- and the UserAttributeService.
- </li>
- </ul>
- </p>
- </subsection>
-
- <subsection name="Utilities and Tools (for working with the Pluto Portal)">
- <p>
- <ul>
- <li>
- <b>Pluto Util:</b>
- Utilities for working with the Pluto Portal. Includes libraries
- for installing pluto, assembling portlet applications for
- deployment in pluto, deploying to pluto, and publishing portlets
- to pluto.
- </li>
- <li>
- <b>Maven Plugin:</b>
- Provides Maven goals for utilizing the Pluto utilities. Install
- the portal within a servlet container, assemble portlets, deploy
- portlets, and publish portlets to th Pluto Portal.
- </li>
- <li>
- <b>Ant Tasks:</b>
- Ant tasks which allow developers to utilize the Pluto utilities
- within ant. Currently supports assembling wars for deployment
- within pluto.
- </li>
- </ul>
- </p>
- </subsection>
-
- </section>
- </body>
-
-</document>
-
+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 Subprojects</title>
+ <author email="ddewolf@apache.org">David DeWolf</author>
+ </properties>
+
+ <body>
+ <section name="Pluto Subprojects">
+
+ <p>
+ Pluto 1.1 utilizes Maven 2 as it's project management and build
+ automation tool. Pluto follows maven's best practices and is organized
+ into modules or subprojects.
+ </p>
+
+ <subsection name="Container Subprojects">
+ <p>
+ <ul>
+ <li>
+ <b>Pluto Container:</b>
+ The Pluto Container is the core compontent of the Apache Pluto
+ project. All other modules either support the development. The
+ Pluto Container is the reference implementation of the Portlet
+ Specification.
+ </li>
+ <li>
+ <b>Pluto Tags:</b>
+ The Java Portlet Tag Library implementation which is provided
+ with the container.
+ </li>
+ </ul>
+ </p>
+ </subsection>
+
+ <subsection name="Portal/Testing Subprojects">
+ <p>
+ <ul>
+ <li>
+ <b>Pluto Portal Driver:</b>
+ A driver library for the Pluto Portlet Container. Provides service
+ implementations and utilities for implementing a portal which
+ utilizes the container.
+ </li>
+ <li>
+ <b>Pluto Portal:</b>
+ The user interface components (web application) of the Pluto
+ Portal. The pluto portal is a simple portal application which
+ embeds the portal. The portal is not meant to be a full enterprise
+ portal, but instead is meant to be an example of how to embed the
+ container and a lightweight environment for developing and testing
+ portlets.
+ </li>
+ <li>
+ <b>Pluto Testsuite:</b>
+ A test portlet which can be used to exercise and test any portlet
+ container.
+ </li>
+ </ul>
+ </p>
+ </subsection>
+
+ <subsection name="Libraries and Supporting Subprojects">
+ <p>
+ <ul>
+ <li>
+ <b>Pluto Descriptor API:</b>
+ A domain model which represents the deployment descriptors read
+ by the portlet container. Contains service interfaces for reading
+ and writing portlet.xml and web.xml.
+ </li>
+ <li>
+ <b>Pluto Descriptor Impl:</b>
+ The default implementation of the Pluto Descriptor API Subproject.
+ The default implementation utilzes castor for reading and writing
+ portlet and web application descriptors.
+ </li>
+ <li>
+ <b>Pluto Optional Services:</b>
+ Provides optional implementations of the Pluto Container Services.
+ Includes database implementations of the PortletPreferencesService
+ and the UserAttributeService.
+ </li>
+ </ul>
+ </p>
+ </subsection>
+
+ <subsection name="Utilities and Tools (for working with the Pluto Portal)">
+ <p>
+ <ul>
+ <li>
+ <b>Pluto Util:</b>
+ Utilities for working with the Pluto Portal. Includes libraries
+ for installing pluto, assembling portlet applications for
+ deployment in pluto, deploying to pluto, and publishing portlets
+ to pluto.
+ </li>
+ <li>
+ <b>Maven Plugin:</b>
+ Provides Maven goals for utilizing the Pluto utilities. Install
+ the portal within a servlet container, assemble portlets, deploy
+ portlets, and publish portlets to th Pluto Portal.
+ </li>
+ <li>
+ <b>Ant Tasks:</b>
+ Ant tasks which allow developers to utilize the Pluto utilities
+ within ant. Currently supports assembling wars for deployment
+ within pluto.
+ </li>
+ </ul>
+ </p>
+ </subsection>
+
+ </section>
+ </body>
+
+</document>
+
Propchange: portals/pluto/trunk/pluto-site/src/site/xdoc/v11/subprojects.xml
------------------------------------------------------------------------------
svn:eol-style = native