portals-pluto-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ddew...@apache.org
Subject svn commit: r355384 - in /portals/pluto/trunk: pluto-portal/src/main/webapp/images/apache-portals.png pluto-site/src/site/xdoc/index.xml
Date Fri, 09 Dec 2005 05:40:42 GMT
Author: ddewolf
Date: Thu Dec  8 21:40:16 2005
New Revision: 355384

URL: http://svn.apache.org/viewcvs?rev=355384&view=rev
Log:
Adding docs updates

Added:
    portals/pluto/trunk/pluto-portal/src/main/webapp/images/apache-portals.png   (with props)
    portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml

Added: portals/pluto/trunk/pluto-portal/src/main/webapp/images/apache-portals.png
URL: http://svn.apache.org/viewcvs/portals/pluto/trunk/pluto-portal/src/main/webapp/images/apache-portals.png?rev=355384&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/pluto/trunk/pluto-portal/src/main/webapp/images/apache-portals.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewcvs/portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml?rev=355384&view=auto
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml (added)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml Thu Dec  8 21:40:16 2005
@@ -0,0 +1,74 @@
+<?xml version="1.0"?>
+<document>
+  <properties>
+    <title>Welcome to Pluto</title>
+    <author email="ddewolf@apache.org">David DeWolf</author>
+  </properties>
+  <body>
+    <section name="Welcome to Pluto">
+
+	  <div class="highlightbox">
+		<p>
+          <a href="http://www.apachecon.com/2005/US/index.html"><img src="http://www.apache.org/images/ac2005us_white_184x80.jpg"
width="184" height="80" border="0" title="ApacheCon US 2005" /></a>
+        </p>
+		<p>
+	    <h5>Pluto Speakers</h5>
+		<ul>
+				<li>David H. DeWolf <br/>
+						<small><a href="http://apachecon.com/2005/US/html/sessions.html#1578">Embedding
Apache Pluto</a></small></li>
+				<li>Carsten Ziegeler - <br/>
+						<small><a href="http://apachecon.com/2005/US/html/sessions.html#1450">Portals@Apache:
Standards <br/> and the Portals Projects</a></small></li>
+        </ul>
+        </p>
+      </div>
+
+     <div class="highlightbox">
+        <h5>Get Pluto 1.0.1</h5>
+        <p>
+          <a href="mirrors.html">
+            <img valign="top" src="http://maven.apache.org/images/folder-open.gif" border="0"
alt="" title="download"/>
+            Download
+          </a>
+          Pluto 1.0.1
+          <small>(12Mb)</small>
+        </p>
+        <ul>
+          <li>
+            <a href="install.html">Installation Guide</a>
+          </li>
+          <li>
+            <a href="resources.html">Installation Instructions</a>
+          </li>
+        </ul>
+      </div>
+
+	  <p>Pluto is the Reference Implementation of the Java Portlet Specfication. The current
version of this specification is JSR 168.</p>
+
+	  <p>Portlets are designed to run in the context of a portal. They are written to
the Portlet API which are similar to the Servlet API.</p>
+
+	  <p>In contrast to servlets, portlets may not do things like sending redirects or
errors to browsers directly, forwarding requests or writing arbitrary markup to the output
stream to assure that they don?t distract the portal web application which uses them. Another
difference compared to servlets is that portlets rely on portal specific infrastructure functions
such as access to user profile information, standard interface for storing/retrieving persistent
settings, getting client information, etc. Generally, portlets are administrated more dynamically
than servlets typically are.</p>
+
+	  <p>A portlet container provides a runtime environment for portlets implemented according
to the Portlet API. In this environment portlets can be instantiated, used and finally destroyed.
The portlet container is not a stand-alone container like the servlet container; instead it
is implemented as a thin layer on top of the servlet container and reuses the functionality
provided by the servlet container.</p>
+
+	  <p>Pluto serves as portlet container that implements the Portlet API and offers
developers a working example platform from which they can test their portlets. However, it's
cumbersome to execute and test the portlet container without a driver, in this case, the portal.
Pluto's simple portal component is built only on the portlet container's and the JSR 168's
requirements. (In contrast, the more sophisticated, Jetspeed project concentrates on the portal
itself rather than the portlet container, and considers requirements from other groups.)</p>
+
+	  </section>
+
+	  <section name="Project Status">
+      <p>Apache Pluto is a subproject of the Apache Portals Project. The current stable
release of Apache Pluto is version 1.0.1. The current version actively being developed is
version 1.1.</p>
+
+      <subsection name="Pluto 1.0.1">
+			  <p>Pluto 1.0.1 is the current stable release of Pluto. This version of pluto is
utilized as the portlet container for Jetspeed and other portals. In addition, Pluto 1.0.1
is embeded within Apache Geronimo.</p>
+	  </subsection>
+
+	  <subsection name="Pluto 1.1">
+        <p>Pluto 1.1 introduces a new container architecture. If you are embedding
Pluto in your portal, realize that 1.1 is not binarily compatible with Pluto 1.0.x.</p>
+
+        <p>Pluto 1.1 aims to simplify the architecture in order to make it more user
and developer friendly. You should find Pluto 1.1 easier to get started with, easier to understand,
and easier to embed with your portal. Your feedback regarding how far we've come is always
welcome on the user and developer mailing lists!</p>
+
+        <p>Pluto 1.1 is currently only available through subversion repository. An
alpha release is currently being considered.</p>
+	  </subsection>
+    </section>
+  </body>
+</document>
+



Mime
View raw message