portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From woon...@apache.org
Subject svn commit: r722405 [12/17] - in /portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade: ./ src/ src/site/ src/site/resources/ src/site/resources/css/ src/site/resources/images/ src/site/resources/images/layouts/ src/site/resources/images/portle...
Date Tue, 02 Dec 2008 08:53:28 GMT
Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-subsites.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-subsites.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-subsites.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-subsites.xml Tue Dec  2 00:53:22 2008
@@ -0,0 +1,374 @@
+<?xml version="1.0"?>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+    
+    http://www.apache.org/licenses/LICENSE-2.0
+    
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<document>
+    <properties>
+        <title>Jetspeed Subsites</title>
+        <subtitle>Guide to Jetspeed Subsites</subtitle>
+        <authors>
+            <person name="David Sean Taylor" email="taylor@apache.org" />
+        </authors>
+    </properties>
+    <body>
+        <section name="What are Subsites?">
+            <p>
+                Subsites are a feature for sub-dividing your portal site map into independent "portal site" trees.
+                This enables use-case scenarios such as hosting two or more Jetspeed portals on the same portal instance (application server).
+                With subsites, subsets of users can be configured to only view a sub-tree, or subsite, of the overall portal site.
+                These users will never see content outside of their subsite.
+                The creation of subsites is based upon profiling rules. You apply profiling rules to navigate users to their subsite root.
+                In this example, 
+            </p>
+        </section>
+        <section name='A Subsite Scenario: Subsite By Hostname'> 
+        <p>In order to direct users to different subsites, you will need to define a set of rules, known as profiling rules.
+        These rules determine which subsite users and guests will visit. 
+        Rules are based on runtime parameters, such as username, roles of the current user, request parameters, session state, or more.
+        In this example we will look at directing users to subsites based on the <b>hostname</b> portion of the URL.
+        Use case scenario we are going to look at are:</p>
+        <ul>
+          <li>A virtual hosting scenario where you are hosting different sites.</li>
+          <li>A single organization with two or more sites, which may also some content in common amongst those subsites.</li>
+        </ul>
+        <subsection name='Virtual Hosting'>
+        <p>In our Virtual Hosting example, we are hosting three different portal subsites:</p>
+        <img src='images/subsites2.jpg' border="0"/>
+        <p>Here we have three subsites (four including localhost) defined for three different companies:
+        </p>
+        <ul>
+        <li>www.company-1.com - the subsite for "Company 1"</li>
+        <li>www.company-2.com - the subsite for "Company 2"</li>
+        <li>www.company-3.com - the subsite for "Company 3"</li>
+        </ul>
+        </subsection>
+        <subsection name='Single Organization'>
+        <p>In our Single Organization example, we are hosting three different portal subsites within the organization:</p>
+        <img src='images/subsites.jpg' border="0"/>        
+        <p>Here we have three subsites (four including localhost) defined for three different companies:
+        </p>
+        <ul>
+        <li>employees.my-company.com - subsite for employees</li>
+        <li>partners.my-company.com - subsite for partners</li>
+        <li>www.my-company.com - subsite for the public</li>
+        </ul>        
+        </subsection>
+        <subsection  name='Site Manager'>
+        <p>The screenshots above show using the Site Manager to configure your subsites.
+        The Site Manager is useful for configuring a live site. When you configure a site initially, 
+        subsites are configured on the file system as folders, subfolders and pages. Optionally, these folders can be imported
+        in the database. See the <a href='guide-psml.html'>Database Page Manager</a> for details on storing subsites in the database.
+        </p>
+        <p>
+        The Site Manager mirrors your file system (or database structure) in a tree view. Looking at the Site View screenshots 
+        above, there are several directories we need to take note of:
+        </p>
+        <ul>
+        <li><b>__subsite-root</b> - this is a reserved directory, containing all subsite control roots</li>
+        <li><b>_hostname</b> - this is a <i>control</i> directory (prefixed with underscore) containing all hostname-based subsites</li>
+        </ul> 
+        <p>Control directories must always begin with an underscore. Profiling rules navigate through control directories based on
+        runtime parameters. In this example, we are creating subsites based on the hostname runtime parameter</p>
+        </subsection>
+        <subsection name='/etc/hosts'>
+        <p>Note that the localhost site is there only for developers. Even developers can simulate a virtual hosting environment
+        by editing their <b>/etc/hosts</b> file on their local machines (on Windows under <b>\windows\system32\drivers\etc\hosts</b>)
+        and making fake entries such as:
+        </p>
+<source>
+<![CDATA[       
+        127.0.0.1 www.company-1.com
+        127.0.0.1 www.company-2.com
+        127.0.0.1 www.company-3.com
+
+        127.0.0.1 employees.my-company.com
+        127.0.0.1 partners.my-company.com
+        127.0.0.1 www.my-company.com
+]]>
+</source>
+        </subsection>
+        </section>
+        <section name="XML Seed Configuration">
+            <p>
+            When initially setting up your Jetspeed portal, you will need to provide initial seed data for your portal.
+            Here we demonstrate how to configure your XML seed data for a subsite.
+            We will be initializing:</p>
+            <ul>
+            <li>Profiling Rules</li>
+            <li>Users</li>
+            </ul>
+            <subsection name='Profiling Rules'>
+            
+<source test="">
+                <![CDATA[
+<ProfilingRule id="subsite-by-hostname" standardRule="false">
+	<description value="A rule based on role fallback algorithm with specified subsite and home page"/>
+	<Criteria>
+		<Criterion name="navigation">
+			<type value="navigation"/>
+			<value value="subsite-root"/>
+			<fallBackOrder value="0"/>
+			<fallBackType value="2"/>
+		</Criterion>
+		<Criterion name="hostname">
+			<type value="hostname"/>
+			<fallBackOrder value="1"/>
+			<fallBackType value="2"/>
+		</Criterion>
+		<Criterion name="user">
+			<type value="user"/>
+			<fallBackOrder value="2"/>
+			<fallBackType value="2"/>
+		</Criterion>
+		<Criterion name="navigation-2">
+			<type value="navigation"/>
+			<value value="subsite-root"/>
+			<fallBackOrder value="3"/>
+			<fallBackType value="2"/>
+		</Criterion>
+		<Criterion name="hostname">
+			<type value="hostname"/>
+			<fallBackOrder value="4"/>
+			<fallBackType value="2"/>
+		</Criterion>
+		<Criterion name="role">
+			<type value="role"/>
+			<fallBackOrder value="5"/>
+			<fallBackType value="2"/>
+		</Criterion>				
+		<Criterion name="path">
+			<type value="path"/>
+			<value value="home"/>
+			<fallBackOrder value="6"/>
+			<fallBackType value="2"/>
+		</Criterion>
+	</Criteria>
+</ProfilingRule>                               
+]]>
+</source>
+<p>A profiling rule contains one or more criterion. Each criterion defines an instruction on how to locate a page in the physical portal site map.
+Criterion of the type <i>navigation</i> are used to navigate down the portal site tree. 
+The <i>fallBackOrder</i> tag should normally just be listed sequential. You can almost always get by with a <i>fallBackType</i> of 2.
+All of the available criterion <i>types</i> are documented in the online <a href='guide-profiler.html'>Profiler Guide</a>.
+The table below describes each criterion in our subsite rule and how it is used in a subsite location algorithm. This rule is a subsite location rule that uses a user-role-fallback algorithm.
+User-role-fallback algorithms first look for a page in the users home directory. If not found there, they then look for a page in each of the users corresponding role directories.
+There are other algorithms provided by out of the box such as role-fallback, group-fallback, mediatype/language fallback. Or you can create your own algorithms by creating new profiling rules in the XML seed data or with
+the Profiler Admininistrative portlet.
+</p>
+<table>
+<tr><th>Name</th><th>Type</th><th>Value</th><th>Description</th></tr>
+<tr><td>navigation</td><td>navigation</td><td>subsite-root</td><td>Navigates to the physical /__subsite-root directory.</td></tr>
+<tr><td>hostname</td><td>hostname</td><td>(provided at runtime)</td><td>Navigates to the control directory /__subsite-root/_hostname, and then to the subdirectory matching the runtime _hostname parameter. If the runtime _hostname parameter equals "localhost", then the physical location is /__subsite-root/_hostname/localhost.</td></tr>
+<tr><td>user</td><td>user</td><td>(provided at runtime)</td><td>Navigates to the control directory /__subsite-root/_hostname/user, and then to the subdirectory matching the runtime _user parameter.  If the runtime _user parameter equals "dean", then the physical location is /__subsite-root/_hostname/localhost/_user/dean.</td></tr>
+<tr><td>navigation-2</td><td>navigation</td><td>subsite-root</td><td>When a page is not found under the user directory, we start over and navigate back to the subsite root.</td></tr>
+<tr><td>hostname</td><td>hostname</td><td>(provided at runtime)</td><td>Then again navigate to the _hostname directory</td></tr>
+<tr><td>role</td><td>role</td><td>(provided at runtime)</td><td>Navigate to each role directory of the given user until we find the page. For example, for a role named "role1", navigate to the control directory /__subsite-root/_hostname/role, and then to the subdirectory matching each runtime _role parameters.  If the runtime _role parameter is only "role1", then the physical location is /__subsite-root/_hostname/localhost/_role/role1.</td></tr>
+<tr><td>path</td><td>path</td><td>home</td><td>This is a constant used in all calculations, the path portion of the URL, such as home.psml, or /accounting/worksheet.psml. It is always appended to the calculated path to give the complete physical address of the page. In the case where there is no page specified, the default value provided in the rule "home" is used, and that actually maps to "home.psml" as the default page extensions.</td></tr>
+</table>
+<p>
+The screenshot below shows the directory tree for a <i>localhost</i> subsite.
+</p>
+<img src='images/localhost-site.jpg'/>
+<p>
+Notice the _user and _role directories. These are control directories based on the runtime parameters <i>user</i> and <i>role</i>.
+The user parameter represents the username of the currently logged on user. The role parameter can represent one or more roles of the current user.
+The subsite algorithm will navigate down to a user directory first, and look in the directory for the current user by name.
+It will look there for name of the current page requested on the URL. 
+Given the following example runtime parameters, the tables below demonstrates the fallback search path algorthm used by the profiler in locating a page given our subsite profiling rule.
+Once it finds the page, the page is immediately returned and the algorithm is terminated.
+For each of the examples below, consider the following runtime parameters:
+<table>
+<tr><td>Username</td><td>dean</td></tr>
+<tr><td>Roles</td><td>role1, role2, role3</td></tr>
+<tr><td>Hostname</td><td>localhost</td></tr>
+</table>
+</p>
+<p>
+<b>http://localhost:8080/jetspeed/portal/calendar.psml</b>
+<table>
+<tr><th>URL</th><th>Site Physical Location</th></tr>
+<tr><td>http://localhost:8080/jetspeed/portal/calendar.psml</td><td>/__subsite-root/_hostname/localhost/_user/dean/calendar.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/_role/role1/calendar.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/_role/role2/calendar.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/_role/role3/calendar.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/calendar.psml</td></tr>
+<tr><td></td><td>/__subsite-root/calendar.psml</td></tr>
+</table>
+</p>
+
+<p>
+<b>http://localhost:8080/jetspeed/portal/accounting/worksheet.psml</b>
+<table>
+<tr><th>URL</th><th>Site Physical Location</th></tr>
+<tr><td>http://localhost:8080/jetspeed/portal/accounting/worksheets.psml</td><td>/__subsite-root/_hostname/localhost/_user/dean/accounting/worksheet.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/_role/role1/accounting/worksheet.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/_role/role2/accounting/worksheet.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/_role/role3/accounting/worksheet.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/accounting/worksheet.psml</td></tr>
+<tr><td></td><td>/__subsite-root/accounting/worksheet.psml</td></tr>
+</table>
+</p>
+
+<p>
+<b>http://localhost:8080/jetspeed/portal/</b>
+<table>
+<tr><th>URL</th><th>Site Physical Location</th></tr>
+<tr><td>http://localhost:8080/jetspeed/portal/</td><td>/__subsite-root/_hostname/localhost/_user/dean/home.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/_role/role1/home.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/_role/role2/home.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/_role/role3/home.psml</td></tr>
+<tr><td></td><td>/__subsite-root/_hostname/localhost/home.psml</td></tr>
+<tr><td></td><td>/__subsite-root/home.psml</td></tr>
+</table>
+</p>
+            </subsection>
+            <subsection name='Associated Rules with Users'>
+<p>
+All users are either explicity or implicity associated with a profiling rule. 
+The User Administration utility has a tab to setup the profiling rule associated with a user:
+</p>            
+<img src='images/user-profile.jpg' border="0"/>
+<p>
+Additionally, you can associate users with profiling rules in the XML seed data configuration:
+</p>
+            <source>
+                <![CDATA[
+<Users>
+...                
+<User name="jetspeed">
+	<credentials password="jetspeed" enabled="TRUE" requiresUpdate="FALSE"/>
+	<roles>manager</roles>
+	<groups>engineering</groups>
+	<preferences/>
+	<userinfo/>
+	<Rules>
+		<Rule locator="menu" rule="role-group"/>
+		<Rule locator="page" rule="role-fallback"/>
+	</Rules>
+</User>
+</Users>                
+]]>
+</source>
+<p>Looking at the <b>Rule</b> element of a User, the locator can be either:</p>
+<ul>
+<li>page - use associated profiling rule to locate pages</li>
+<li>menu - use the associated profiling rule to locate menus (if not specified, use the page locator)</li>
+</ul>
+<p>The <b>rule</b> attribute on the <b>Rule</b> element of a User defines which profiling rule is associated to either a page or menu locator.
+If a user is not associated with a locator, then there is a system wide locator configured in the Spring configuration file <i>profiler.xml</i>.
+See the contructor-arg of index = 1. This locator is the default locator, system-wide, for when there is no-associated profiling rule.
+Normally, profiling rules are associated with user during activities such as the creation of new users with the User Administration portlet,
+or during new user registration.
+</p>
+<source>
+<![CDATA[
+<beans>
+    <!-- Profiler -->
+    <bean id="profilerImpl" class="org.apache.jetspeed.profiler.impl.JetspeedProfilerImpl" init-method="init">
+        <constructor-arg index="0">
+            <value>JETSPEED-INF/ojb/profiler_repository.xml</value>
+        </constructor-arg>
+        <constructor-arg index="1">
+            <value>j2</value>
+        </constructor-arg>                
+        ....
+]]>
+</source>
+            </subsection>            
+        </section>
+        <section name="Hostname Profiling Rule Configuration">
+            <p>
+There is an option for hostnames to use the entire hostname or a prefix.            
+This is configured in the Spring configuration file <i>profiler.xml</i>.
+            </p>
+            <source>
+                <![CDATA[                
+    <bean id='HostnameCriterionResolver' class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
+      <!--  use the dot prefix, for ex: "accounting.xyz.com" returns "accounting" -->
+      <constructor-arg type="boolean" index="0">
+            <value>false</value> 
+        </constructor-arg>    	
+    </bean>                    
+]]>
+            </source>
+            <p>
+By settting the prefix boolean argument to true, the hostname resolve will only look at the prefix of the hostname.
+For example, with the dot prefix flag set to true, a hostname of "accounting.xyz.com" returns "accounting".            
+            </p>            
+        </section>
+        <section name="Administering Subsites with the User Manager">
+            <p>When creating a new user from User Manager Administration, you can specify two fields to enable and configure subsite behavior for that new user:
+        	</p>
+        	<ul>
+        	<li><b>Profiling Rule:</b> choose a profiling rule to assign to the new user that has built in subsite support such as the example used in this document: <b>subsite-by-hostname</b>.</li>
+        	<li><b>Subsites:</b> from the dropdown select the subsite to assign as the home subsite to the new user, or leave blank to use default /_user home.</li>
+        	</ul>
+        <img src='images/newuser-subsite-admin.png' border="0"/>        
+        	<p>When using the <b>subsite-by-hostname</b> profiling rule, make sure to select a subsite from the subsites drop-down, as these two attributes work together.
+        	The rule is the instructions on where to look for home pages, and the subsite selection tells the profiling rule which subsite will hold this user directory</p>
+        	<p>Subsite management can also be delegated to managers of particular subsites. For example, you may want to setup User Manager Administration pages for each subsite.
+        	By modifying the deployment descriptor for the j2-admin application, each User Manager details portlet can be configured with a different default subsite:</p>
+        <img src='images/subsite-fields.png' border="0"/>                        	        	
+       </section> 	
+        <section name="Administering Subsites with User Registration">
+            <p>When creating a new user from the User Registration portlet, you can specify two fields to enable and configure subsite behavior for that new user:
+        	</p>
+        	<ul>
+        	<li><b>rulesValues:</b> choose a profiling rule to assign to the new user that has built in subsite support such as the example used in this document: <b>subsite-by-hostname</b>.</li>
+        	<li><b>subsiteRootFolder:</b> the full path to one unique subsite root folder.</li>
+        	</ul>        	
+        <img src='images/user-reg-subsite.png' border="0"/>                        	
+        	<p>NOTE: the User Registration portlet will store these preference values on a per user basis. Usually this means the preferences are stored for the administrative user only.
+        	If you will have administrators registering users, then this approach works fine. However, with <b>self-registration</b> portal, you will need to set these values in the defaults for the portlet.
+        	The defaults are usually set in the portlet.xml, for example:
+        	</p>
+<source>
+<![CDATA[                
+...
+        <preference>
+     		<name>subsiteRootFolder</name>
+            <value>/__subsite-root/_hostname/localhost</value>   
+        </preference>        
+        <preference>
+     		<name>rulesNames</name>
+            <value>page</value>   
+        </preference>        
+        <preference>
+     		<name>rulesValues</name>
+            <value>subsite-by-hostname</value>   
+        </preference>        
+...
+]]>
+</source>        	
+        	<p>You can also set defaults on a per page (PSML) intermediate level:</p>
+<source>
+<![CDATA[                
+    <fragment id="example-subsite-1" type="portlet" name="j2-admin::UserRegistrationPortlet">
+      <preference name="subsiteRootFolder">
+        <value>/__subsite-root/_hostname/localhost</value>
+      </preference>
+      <preference name="rulesNames">
+        <value>page</value>
+      </preference>
+      <preference name="rulesValues">
+        <value>subsite-by-hostname</value>
+      </preference>      
+    </fragment>
+]]>
+</source>        	
+		</section>       
+    </body>
+</document>

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-subsites.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-subsites.xml
------------------------------------------------------------------------------
    svn:keywords = Id

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-tomcat-sso-cross-context-j2-realm.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-tomcat-sso-cross-context-j2-realm.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-tomcat-sso-cross-context-j2-realm.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-tomcat-sso-cross-context-j2-realm.xml Tue Dec  2 00:53:22 2008
@@ -0,0 +1,102 @@
+<?xml version="1.0"?>
+<!--
+	Licensed to the Apache Software Foundation (ASF) under one or more
+	contributor license agreements.  See the NOTICE file distributed with
+	this work for additional information regarding copyright ownership.
+	The ASF licenses this file to You under the Apache License, Version 2.0
+	(the "License"); you may not use this file except in compliance with
+	the License.  You may obtain a copy of the License at
+	
+	http://www.apache.org/licenses/LICENSE-2.0
+	
+	Unless required by applicable law or agreed to in writing, software
+	distributed under the License is distributed on an "AS IS" BASIS,
+	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+	See the License for the specific language governing permissions and
+	limitations under the License.
+-->
+<document>
+	<properties>
+		<title>Tomcat SSO and Cross Context Webapps Guide</title>
+		<subtitle>Documentation for using the Jetspeed Authentication accross multiple webapps running in the same Tomcat container</subtitle>
+		<authors>
+			<person name="Philip Mark Donaghy" email="philip.donaghy@gmail.com" />
+		</authors>
+	</properties>
+	<body>
+		<section name="Sharing the Jetspeed Realm Across Tomcat Webapps">
+			<p>
+				This guide provides a tutorial for creating a shared authentication Realm
+				between multiple webapps running in the same Tomcat(&gt;=5.5) container.
+			</p>
+			<subsection name="1. The Jetspeed Realm">
+				<p>
+				Realms are configured in the Engine element of $CATALINA_HOME/conf/server.xml. Move the Jetspeed Realm element from $CATALINA_HOME/conf/Catalina/localhost/jetspeed.xml to $CATALINA_HOME/conf/server.xml replacng or commenting out the UserDatabase Realm. 
+				<source><![CDATA[
+<Realm className="org.apache.catalina.realm.JAASRealm"
+           appName="Jetspeed"
+           userClassNames="org.apache.jetspeed.security.impl.UserPrincipalImpl"
+           roleClassNames="org.apache.jetspeed.security.impl.RolePrincipalImpl"
+           useContextClassLoader="false"
+           debug="0"/>]]>
+				</source>
+				</p>
+			</subsection>
+			<subsection name="2. Enable the Tomcat SingleSignOn Valve">
+			<p>
+			Uncomment the Tomcat single sign on Valve in $CATALINA_HOME/conf/server.xml.
+			<source><![CDATA[
+<Host name="localhost" appBase="webapps">
+    <!-- Enable tomcat SSO *** -->
+    <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
+</Host>]]>
+			</source>
+			</p>
+			</subsection>
+			<subsection name="3. Each web.xml">
+			<p>
+			Create a security-constraint in each webapp web.xml descriptor.
+			<source><![CDATA[
+  <security-constraint>
+    <web-resource-collection>
+       <web-resource-name>Whatever</web-resource-name>
+       <url-pattern>/*</url-pattern>
+    </web-resource-collection>
+    <auth-constraint>
+      <role-name>manager</role-name>
+    </auth-constraint>
+  </security-constraint>
+
+  <!-- Define the Login Configuration for this Application -->
+  <login-config>
+    <auth-method>BASIC</auth-method>
+    <realm-name>Jetspeed</realm-name>
+  </login-config>
+
+  <!-- Security roles referenced by this web application -->
+  <security-role>
+    <description>
+        The role that is required to log in to the Manager Application
+    </description>
+    <role-name>manager</role-name>
+  </security-role>]]>
+			</source>
+			</p>
+			</subsection>
+			<subsection name="4. Known Issues">
+			<p>
+			1. The default Tomcat Realm must be replaced, removed, or commented out. A known side effect of this prevents the Tomcat manager application from working. It can be resolved by using the Jetspeed realm in $CATALINA_HOME/server/webapps/manager/manager.xml.
+			<source><![CDATA[
+  <login-config>
+    <auth-method>BASIC</auth-method>
+    <realm-name>Jetspeed</realm-name>
+  </login-config>]]>
+			</source>
+			</p>
+			<p>
+			2. Authentication must be made in Jetspeed before accessing other webapps.
+			</p>
+			</subsection>
+		</section>
+	</body>
+</document>

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-tomcat-sso-cross-context-j2-realm.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-tomcat-sso-cross-context-j2-realm.xml
------------------------------------------------------------------------------
    svn:keywords = Id

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-user-attributes.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-user-attributes.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-user-attributes.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-user-attributes.xml Tue Dec  2 00:53:22 2008
@@ -0,0 +1,142 @@
+<?xml version="1.0"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<document>
+  <properties>
+    <title>Guide to Defining User Attributes</title>
+    <subtitle>PLT.17 User Information Configuration</subtitle>
+    <authors>
+      <person name="Ate Douma" email="ate@douma.nu"/>
+    </authors>
+  </properties>
+  <body>
+    <section name="Defining User Attributes">
+      <p>
+        The Portlet Specification defines how Portlet Applications can use User Attributes.<br/>
+        The attributes must be defined in the portlet.xml like (see PLT.17.1):</p>
+      <source><![CDATA[
+<portlet-app version="1.0" xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd">
+   <user-attribute>
+      <description>User Given Name</description>
+      <name>user.name.given</name>
+   </user-attribute>
+   <user-attribute>
+      <description>User Last Name</description>
+      <name>user.name.family</name>
+   </user-attribute>
+   <user-attribute>
+      <description>User eMail</description>
+      <name>user.home-info.online.email</name>
+   </user-attribute>
+   ...
+</portlet-app>]]></source>
+      <p>
+        Once attributes are defined like this, a portlet can access the current values for the logged on
+        user as an unmodifiable Map from the PortletRequest using the USER_INFO constant defined in the
+        PortletRequest interface (see PLT.17.2):</p>
+      <source>
+Map userInfo = (Map)request.getAttribute(PortletRequest.USER_INFO);
+String givenName = (userInfo!=null) ? (String)userInfo.get("user.name.given") : "";
+String lastName = (userInfo!=null) ? (String)userInfo.get("user.name.family") : "";
+String email = (userInfo!=null) ? (String)userInfo.get("user.home-info.online.email") : "";</source>
+      <p>
+        What is not defined by the Portlet Specification is <em>how</em> the Portal
+        must map the defined User Attributes to concrete attributes of a user.</p>
+    </section>
+    <section name="Mapping User Attributes">
+      <p>
+        Jetspeed-2 provides a very flexible way to define concrete User attributes and defining access to them.</p>
+      <p>
+        Concrete User attributes are stored using User Preferences for which Jetspeed-2 provides its own database
+        back end for storage (which is customizable by the way like almost any component of Jetspeed-2).  The user
+        attributes implementation leverages Jetspeed's 
+        <a href="../multiproject/jetspeed-prefs/index.html">java.util.prefs.Preferences</a> implementation.<br/>
+        The concrete User attributes are stored under a specific node in the User preferences and can contain
+        any named attribute at will.<br/>
+        These concrete User attributes can be mapped to the defined User Attributes in the portlet.xml in two ways:
+        <ol>
+          <li>
+            Using an exact match of attribute names 
+          </li>
+          <li>
+            Using a custom mapping definition in a jetspeed-portlet.xml 
+          </li>
+        </ol> 
+      </p>
+      <subsection name="Custom User Attribute Mapping">
+        <p>
+          If you write new Portlet Applications with Jetspeed-2 as target Portal, defining User Attributes which
+          match the concrete User attributes in the Portal usually will be quite straightforward<br/>
+          But, if you have an existing Portlet Application which you want to deploy on Jetspeed-2, there might
+          be a mismatch between the attribute names needed by the Portlet Application and the
+          concrete attribute names as stored in the Jetspeed-2 User Preferences.</p>
+        <p>
+          <em>
+            Note: The Portlet Specification defines a set of attribute names which are recommended to be used
+            in Appendix PLT.D.<br/>
+            Portlet Applications using these attribute names and Portals storing the concrete User attributes
+            also using these names won't need any custom attribute mapping as will be described below.<br/>
+            Although Jetspeed-2 allows a fully free definition of the concrete User attributes,
+            it is recommended to use these predefined attributes names as much as possible.</em></p>
+        <p>
+          The jetspeed-portlet.xml allows jetspeed specific configurations and customizations to be specified.<br/>
+          This deployment document isn't required, but will be processed if found within the WEB-INF folder of a 
+          Portlet Application war.<br/>
+          Jetspeed specific configurations must be defined using the "http://portals.apache.org/jetspeed" namespace.</p>
+        <p>
+          User attribute mapping is defined using an "user-attribute-ref" element containing a "name" element defining
+          the custom user attribute name and a "name-link" element defining the concrete attribute name to which it
+          is mapped:</p>
+        <source><![CDATA[
+<portlet-app version="1.0" 
+   xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd" 
+   xmlns:js="http://portals.apache.org/jetspeed"> 
+   <js:user-attribute-ref>
+      <js:name>user-name-given</js:name>
+      <js:name-link>user.name.given</js:name-link>
+   </js:user-attribute>
+   <js:user-attribute-ref>
+      <js:name>user-name-family</js:name>
+      <js:name-link>user.name.family</js:name-link>
+   </js:user-attribute>
+   ...
+</portlet-app>]]></source>
+        <p>
+          Using the above custom mapping as an example, the Portlet can now access the user attributes as follows:</p>
+        <source>
+Map userInfo = (Map)request.getAttribute(PortletRequest.USER_INFO);
+String givenName = (userInfo!=null) ? (String)userInfo.get("user-name-given") : "";
+String lastName = (userInfo!=null) ? (String)userInfo.get("user-name-family") : "";
+String email = (userInfo!=null) ? (String)userInfo.get("user.home-info.online.email") : "";</source>
+        <p>
+          Note that the email attribute for which no custom mapping was defined still can be access using
+          exact name matching (provided the concrete attribute is defined for the logged on user).</p>
+      </subsection>  
+    </section>
+    <section name="Defining User Attributes in Jetspeed-2">
+      <p>
+        Jetspeed-2 is provided with several Administrative Portlets, including for User Management.<br/>
+        Using the User Management Portlets, it is very easy to define or modify concrete attributes for a user:</p>      
+      <img src="../images/definingUserAttributes.jpg"/>
+      <p>
+        The User Info Test demo Portlet, default deployed in Jetspeed-2 and displayed on the start page, uses
+        the above example User Attribute definitions and displays the values for the logged on user (also showing that
+        these can be accessed from both the PortletRequest as well as the HttpServletRequest from within a servlet):</p>
+      <img src="../images/usingUserAttributes.jpg"/>
+    </section>
+  </body>
+</document>

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-user-attributes.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-user-attributes.xml
------------------------------------------------------------------------------
    svn:keywords = Id

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/create-patch.gif
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/create-patch.gif?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/create-patch.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/j2-overview.gif
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/j2-overview.gif?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/j2-overview.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/jetspeedservlet-c.gif
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/jetspeedservlet-c.gif?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/jetspeedservlet-c.gif
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/localhost-site.jpg
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/localhost-site.jpg?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/localhost-site.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/newuser-subsite-admin.png
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/newuser-subsite-admin.png?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/newuser-subsite-admin.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/pages.jpg
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/pages.jpg?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/pages.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/parameter-resolution-2.jpg
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/parameter-resolution-2.jpg?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/parameter-resolution-2.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/parameter-resolution.jpg
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/parameter-resolution.jpg?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/parameter-resolution.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/profiler-pipeline.jpg
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/profiler-pipeline.jpg?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/profiler-pipeline.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/user-profile-locator.jpg
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/user-profile-locator.jpg?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/profiler/user-profile-locator.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/subsite-fields.png
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/subsite-fields.png?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/subsite-fields.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/subsites.jpg
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/subsites.jpg?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/subsites.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/subsites2.jpg
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/subsites2.jpg?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/subsites2.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/user-profile.jpg
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/user-profile.jpg?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/user-profile.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/user-reg-subsite.png
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/user-reg-subsite.png?rev=722405&view=auto
==============================================================================
Binary file - no diff available.

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/images/user-reg-subsite.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/index.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/index.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/index.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/index.xml Tue Dec  2 00:53:22 2008
@@ -0,0 +1,91 @@
+<?xml version="1.0"?>
+<!--
+	Licensed to the Apache Software Foundation (ASF) under one or more
+	contributor license agreements.  See the NOTICE file distributed with
+	this work for additional information regarding copyright ownership.
+	The ASF licenses this file to You under the Apache License, Version 2.0
+	(the "License"); you may not use this file except in compliance with
+	the License.  You may obtain a copy of the License at
+	
+	http://www.apache.org/licenses/LICENSE-2.0
+	
+	Unless required by applicable law or agreed to in writing, software
+	distributed under the License is distributed on an "AS IS" BASIS,
+	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+	See the License for the specific language governing permissions and
+	limitations under the License.
+-->
+<document>
+	<properties>
+		<title>Documentation Guides Index</title>
+		<subtitle>Jetspeed-2 Documentation Guides</subtitle>
+		<authors>
+			<person name="David Le Strat" email="dlestrat@apache.org" />
+		</authors>
+	</properties>
+	<body>
+		<section name="Documentation Guides">
+		<subsection name="Getting Started">
+		<ul>
+			<li><a href="../getting-started.html">Getting started guide</a></li>
+			<li><a href="../getting-started-source.html">Getting started with Jetspeed-2 source guide</a></li>
+		</ul>
+		</subsection>
+		<subsection name="Guides to Portal Concepts">
+		<ul>
+			<li><a href="guide-pipeline.html">Guide to Jetspeed-2 pipeline</a></li>
+			<li><a href="guide-decorators.html">Guide to decorators</a></li>
+			<li><a href="guide-layouts.html">Guide to layouts</a></li>
+		</ul>
+		</subsection>
+		<subsection name="Configuration Guides">
+		<ul>
+			<li><a href="guide-security.html">Guide to configuring Jetspeed-2 security</a></li>
+			<li><a href="guide-sso.html">Guide to using Jetspeed-2 single sign-on</a></li>
+		  <li><a href="guide-ntlm.html">Guide to using NTLM Authentication</a></li>
+		  <li><a href="guide-user-attributes.html">Guide to defining user attributes (PLT.17 user information configuration)</a></li>
+			<li><a href="guide-profiler.html">Guide to using profilers</a></li>
+			<li><a href="guide-aggregation.html">Guide to Aggregation</a></li>
+			<li><a href="guide-subsites.html">Guide to Subsites</a></li>
+			<li><a href="guide-migration.html">Guide to Migration</a></li>			
+		</ul>
+		</subsection>
+		<subsection name="Portal Development Guides">
+		<ul>
+			<li><a href="guide-portal-design.html">Guide to portal design</a></li>
+			<li><a href="guide-psml.html">Guide to PSML</a></li>
+			<li><a href="guide-security-declarative-psml.html">Guide to declarative security through PSML</a></li>
+			<li><a href="guide-menus-declarative-psml.html">Guide to declarative menus in PSML</a></li>
+			<li><a href="guide-site.html">Guide to working with a Jetspeed-2 site</a></li>
+			<li><a href="guide-l10n.html">Guide to localization with Jetspeed-2</a></li>
+			<li><a href="guide-ajax-api.html">Guide to Jetspeed-2 AJAX API</a></li>
+			<li><a href="guide-simple-portlet.html">Guide to a very simple portlet with Jetspeed-2</a></li>
+			<li><a href="guide-simple-velocity-portlet.html">Guide to a very simple velocity portlet with Jetspeed-2</a></li>
+			<li><a href="guide-simple-jsf-portlet.html">Guide to a very simple jsf portlet with Jetspeed-2</a></li>
+			<li><a href="guide-portlet-bridges.html">Guide to portlet bridges</a></li>				
+			<li><a href="guide-profiling-ip.html">Guide to Profiling IP Addresses</a></li>			
+		</ul>
+		</subsection>
+		<subsection name="Jetspeed-2 Development Guide">
+		<ul>
+			<li><a href="guide-j2-development.html">Guide to Jetspeed-2 development</a></li>
+			<li><a href="../how-to-help.html">Guide to helping with Jetspeed-2</a></li>
+			<li><a href="guide-tomcat-sso-cross-context-j2-realm.html">Tomcat SSO and Cross Context Webapps Guide</a></li>
+		</ul>
+		</subsection>
+		<subsection name="Guides to Jetspeed-2 Tools">
+		<ul>
+			<li><a href="guide-jpt.html">Guide to Jetspeed-2 Power Tools</a></li>
+			<li><a href="../components/jetspeed-deploy-tools/index.html">Guide to Jetspeed-2 Portlet Application Deployment</a></li>
+			<li><a href="../maven/index.html">Guide to Jetspeed-2 Maven Plugins</a></li>			
+		</ul>
+		</subsection>
+		<subsection name="Components Guides">
+		<ul>
+			<li><a href="guide-components.html">Guide to Jetspeed-2 component architecture</a></li>
+			<li><a href="guide-dir-structure.html">Guide to Jetspeed-2 directory structure</a></li>
+		</ul>
+		</subsection>		
+		</section>
+	</body>
+</document>

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/index.xml
------------------------------------------------------------------------------
    svn:keywords = Id

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/how-to-help.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/how-to-help.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/how-to-help.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/how-to-help.xml Tue Dec  2 00:53:22 2008
@@ -0,0 +1,79 @@
+<?xml version="1.0"?>
+<!--
+	Licensed to the Apache Software Foundation (ASF) under one or more
+	contributor license agreements.  See the NOTICE file distributed with
+	this work for additional information regarding copyright ownership.
+	The ASF licenses this file to You under the Apache License, Version 2.0
+	(the "License"); you may not use this file except in compliance with
+	the License.  You may obtain a copy of the License at
+	
+	http://www.apache.org/licenses/LICENSE-2.0
+	
+	Unless required by applicable law or agreed to in writing, software
+	distributed under the License is distributed on an "AS IS" BASIS,
+	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+	See the License for the specific language governing permissions and
+	limitations under the License.
+-->
+<document>
+	<properties>
+		<title>How to Help?</title>
+		<subtitle>How to Help?</subtitle>
+		<authors>
+			<person name="David Le Strat" email="dlestrat@apache.org" />
+		</authors>
+	</properties>
+	<body>
+		<section name="How to Help?">
+		<subsection name="Simple Things I Can Do to Help">
+		<p>
+		There are many ways to help with Jetspeed-2 as with most open source projects:
+		<ul>
+		<li>Subscribe to the <a href="mail-lists.html">user mailing list</a> and help answer questions from the community.
+		In open source a thriving community makes the project successful.  Don't be shy to ask basic questions, we have all
+		been there.</li>
+		<li>Report bugs and issues that you encounter in <a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10492">Jetspeed-2 bug tracking system</a>.
+		Prior to reporting a bug, make sure to discuss the issue on the <a href="mail-lists.html">user mailing list</a> or even the 
+		<a href="mail-lists.html">developer mailing list</a>.</li>
+		<li>When you encounter an issue, you may be compelled to fix it.  We encourage this as this makes for a vibrant
+		community.  Once you have a fix, <a href="guides/guide-j2-development.html">submit a patch</a> on the reporting issue.</li>
+		</ul>
+		</p>
+		</subsection>
+		<subsection name="Why Should I Get Involved?">
+		<p>
+		There are many reasons why you want to help, just a few strong points:
+		<ul>
+		<li>If you help others solve there issues, they will most likely help you when you run into some problems.</li>
+		<li>By contributing patches, you can influence the prioritization of functionality and get your changes incorporated.</li>
+		<li>By reporting issues, you help Jetspeed-2 become a stronger project and improve its quality overall.</li>
+		<li>You will meet and get to know great people as well as share and learn best practices which will help you on
+		your project.</li>
+		</ul>
+		We are looking forward to have you part of our community!
+		</p>
+		</subsection>
+		<subsection name="How do I Join the Project?">
+		<p>
+		Projects at Apache operate under a <a href="http://www.apache.org/foundation/how-it-works.html#meritocracy">meritocracy</a>.
+		To become a committer, you first need to demonstrate your committment.  The best way to do so is to start contributing patch,
+		participate in the community and make your interest known.  It takes time and willingness to help and contribute!  This may
+		seem a bit intimidating at first, but the community will always help people who show interest and committment.
+		</p>
+		</subsection>
+		<subection name="Other Resources for Help">
+		<p>
+		Here are some useful links for other resources for help.
+		<ul>
+		<li><a href="http://portals.apache.org/development/code-standards.html">Portals project coding standards</a>.</li>
+		<li><a href="http://portals.apache.org/development/documentation.html">Portals project documentation standards</a>.</li>
+		<li><a href="http://www.apache.org/foundation/how-it-works.html">How does the Apache Software Foundation work</a>?</li>
+		<li><a href="http://people.apache.org/~coar/mlists.html#portals.apache.org">Portals mailing lists statistics</a>.  This can be helpful
+		to help you decide which mailing list to subscribe to.</li>
+		</ul>
+		</p>
+		</subection>
+		</section>
+	</body>
+</document>
+

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/how-to-help.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/how-to-help.xml
------------------------------------------------------------------------------
    svn:keywords = Id

Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/index.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/index.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/index.xml Tue Dec  2 00:53:22 2008
@@ -0,0 +1,158 @@
+<?xml version="1.0"?>
+<!--
+	Licensed to the Apache Software Foundation (ASF) under one or more
+	contributor license agreements.  See the NOTICE file distributed with
+	this work for additional information regarding copyright ownership.
+	The ASF licenses this file to You under the Apache License, Version 2.0
+	(the "License"); you may not use this file except in compliance with
+	the License.  You may obtain a copy of the License at
+	
+	http://www.apache.org/licenses/LICENSE-2.0
+	
+	Unless required by applicable law or agreed to in writing, software
+	distributed under the License is distributed on an "AS IS" BASIS,
+	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+	See the License for the specific language governing permissions and
+	limitations under the License.
+-->
+<document>
+	<properties>
+		<title>Jetspeed 2 Home Page</title>
+		<subtitle>Welcome to Jetspeed 2</subtitle>
+		<authors>
+			<person name="David Sean Taylor" email="taylor@apache.org" />
+			<person name="David Le Strat" email="dlestrat@apache.org" />
+		</authors>
+	</properties>
+	<body>
+		<section name="Welcome to Jetspeed-2">
+			<div id="downloadbox">
+				<h5>Get Jetspeed 2.1.3</h5>
+				<p>
+					<a href="download.html">
+						<img valign="top" src="images/folder-open.gif"
+							border="0" alt="" title="download" />
+						Download
+					</a>
+					Jetspeed 2.1.3
+					<small>(35MB)</small>
+				</p>
+				<ul>
+					<li>
+						<a href="getting-started.html#System_Requirements">
+							System Requirements
+						</a>
+					</li>
+					<li>
+						<a
+							href="getting-started-installer.html">
+							Installation Instructions
+						</a>
+					</li>
+					<li>
+						<a href="release-notes.html">Release Notes</a>
+					</li>
+					<li>
+						<a href="features.html">Features</a>
+					</li>
+					<li>
+						<a href="guides/index.html">
+							Getting Started
+						</a>
+					</li>
+					<li>
+						<a href="guides/guide-migration.html">
+							Migrating Guide
+						</a>
+					</li>
+					<li>
+						<a href="guides/guide-demo.html">
+							Live demo!
+						</a>
+					</li>
+				</ul>
+			</div>
+			<p>
+				Jetspeed-2 is the next-generation enterprise portal at
+				Apache. Jetspeed-2 offers several architectural
+				enhancements and improvements over Jetspeed 1.0. First,
+				Jetspeed-2 is conformant to the
+				<a href="http://www.jcp.org/en/jsr/detail?id=168">Java Portlet Standard</a> 
+				and provides a standard mechanism for the deployment
+				of portlets. Second, Jetspeed-2 has matured to a more
+				scalable architecture featuring multi-threaded
+				functionality. Third, Jetspeed-2 is decoupled from
+				several legacy open source projects. Fourth, Jetspeed-2
+				is based on a component architecture.
+				<br/><br/>
+			</p>
+			<subsection name="Jetspeed-2 Documentation">
+			<p>
+				Most Jetspeed-2 documentation is in the form of
+				<a href="guides/index.html">documentation guides</a>
+				.
+			</p>
+			</subsection>
+			<subsection name="Jetspeed-2 Status">
+				<p>
+					The latest 2.1.3 production release of Jetspeed-2 was released
+					on December 21, 2007.  Future development areas include alignment with the upcoming
+					<a href="http://www.jcp.org/en/jsr/detail?id=286">Java Portlet Standard 2.0, JSR-286</a>
+				    new portlet applications, WSRP support, further improvement of the design and user experience.
+				</p>
+			</subsection>
+			<subsection name="About Jetspeed-2">
+				<p>
+Jetspeed is an Open Portal Platform and Enterprise Information Portal, written entirely in open source under the Apache license in Java and XML.
+Jetspeed is an open component portal architecture based on standards. All access to the portal is managed through a robust portal security policy.
+Within a Jetspeed portal, individual portlets can be aggregated to create a page. Each portlet is an independent application with 
+Jetspeed acting as the central hub making information from multiple sources available in an easy to use manner.
+				</p>
+				<p>
+A portal based on Jetspeed can make applications, database information and other data sources available to end-users through a single web site. 
+Jetspeed provides a security infrastructure so that the information and functions made available to each user can be customized on basis of the
+ user or a role that the user has. The user can access the portal via a web browser, WAP-phone, pager or any other device supported by the servlet engine.
+				</p>
+				<p>
+				</p>
+				<p>
+					For more information, see:
+					<ul>
+						<li>
+							<a href="developers.html">
+								Jetspeed for Developers
+							</a>
+							?
+						</li>
+						<li>
+							How do I
+							<a href="getting-started.html">
+								Get Started
+							</a>
+							?
+						</li>
+						<li>
+							Where is
+							<a href="guides/index.html">
+								the Documentation Guides
+							</a>
+							?
+						</li>
+						<li>
+							How
+							<a href="how-to-help.html">Can I Help</a>
+							?
+						</li>
+						<li>
+							What do I need to know
+							<a href="j1-users.html">
+								if I used Jetspeed-1
+							</a>
+							?
+						</li>
+					</ul>
+				</p>
+			</subsection>
+		</section>
+	</body>
+</document>
\ No newline at end of file

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/index.xml
------------------------------------------------------------------------------
    svn:keywords = Id



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message