Author: rwatler
Date: Tue Apr 20 09:57:11 2010
New Revision: 935850

URL: http://svn.apache.org/viewvc?rev=935850&view=rev
Log:
correct broken multiproject links

Removed:
    
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-components.xml
Modified:
    
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/credentials.xml
    
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml
    
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-user-attributes.xml
    
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/credentials.xml
    
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-database.xml
    
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-decorators.xml
    
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-portlet-bridges.xml
    
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-simple-velocity-portlet.xml

Modified: 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/credentials.xml
URL: 
http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/credentials.xml?rev=935850&r1=935849&r2=935850&view=diff
==============================================================================
--- 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/credentials.xml
 (original)
+++ 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/credentials.xml
 Tue Apr 20 09:57:11 2010
@@ -34,7 +34,7 @@
             configuration file.</p>
             <subsection name="LoginValidationValveImpl">
               <p>
-              The <a 
href="../multiproject/jetspeed-portal/apidocs/org/apache/jetspeed/security/impl/LoginValidationValveImpl.html">
+              The <a 
href="../apidocs/org/apache/jetspeed/security/impl/LoginValidationValveImpl.html">
               <code>LoginValidationValveImpl</code></a> provides feedback to 
the user about the cause of an failed login
               attempt.</p>
               <p>
@@ -44,7 +44,7 @@
               presented to the user.</p>
               <p>
               The following possible error codes can be returned (all defined 
in the
-              <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/login/LoginConstants.html">
+              <a 
href="../apidocs/org/apache/jetspeed/login/LoginConstants.html">
               <code>LoginConstants</code></a> interface):</p>
               <ol>
                 <li>ERROR_UNKNOWN_USER</li>
@@ -77,7 +77,7 @@
             </subsection>
             <subsection name="PasswordCredentialValveImpl">
               <p>
-              The <a 
href="../multiproject/jetspeed-portal/apidocs/org/apache/jetspeed/security/impl/PasswordCredentialValveImpl.html">
+              The <a 
href="../apidocs/org/apache/jetspeed/security/impl/PasswordCredentialValveImpl.html">
               <code>PasswordCredentialValveImpl</code></a> is meant to be used 
together with a special Portlet on a
               special Portal Page (PSML) to automatically request or even 
require a user to change its password.</p>
               <p>
@@ -114,7 +114,7 @@
               <p>
               To be able to automatically provide the user with this 
information and allow or require the password to
               be changed directly after login, a special 
<code>ProfileLocator</code> 
-              <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/profiler/ProfileLocator.html#SECURITY_LOCATOR">
+              <a 
href="../apidocs/org/apache/jetspeed/profiler/ProfileLocator.html#SECURITY_LOCATOR">
               <code>SECURITY_LOCATOR</code></a> is used. The 
<code>PageProfilerValve</code> (which should be configed
               <em>after</em> this valve in the pipeline) will then use this 
enforced locator to be used to find the
               related portal page to present to the user.</p>
@@ -133,7 +133,7 @@
               <p>
               The <code>ChangePasswordPortlet</code> works together with the 
<code>PasswordCredentialValveImpl</code>
               as it checks for the 
-                <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/security/PasswordCredential.html#PASSWORD_CREDENTIAL_DAYS_VALID_REQUEST_ATTR_KEY">
+                <a 
href="../apidocs/org/apache/jetspeed/security/PasswordCredential.html#PASSWORD_CREDENTIAL_DAYS_VALID_REQUEST_ATTR_KEY">
               <code>PASSWORD_CREDENTIAL_DAYS_VALID_REQUEST_ATTR_KEY</code></a> 
request parameter which will be set by
               this valve with the number of days the password is still valid. 
For a required password change this will
               be set to Integer(0).</p>

Modified: 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml
URL: 
http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml?rev=935850&r1=935849&r2=935850&view=diff
==============================================================================
--- 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml
 (original)
+++ 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-menus-declarative-psml.xml
 Tue Apr 20 09:57:11 2010
@@ -411,16 +411,16 @@ data HTML elements that make up each dis
 </p>
 <p>
 The declarative menu Portal Site Component objects exposed to the layout 
decorators are documented in the 
-<a href="../multiproject/jetspeed-api/apidocs/index.html">Jetspeed API</a>. 
Here is a list of the primary interfaces
+<a href="../apidocs/index.html">Jetspeed API</a>. Here is a list of the 
primary interfaces
 that make up this interface:
 <ul>
-       <li><a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/portalsite/Menu.html">org.apache.jetspeed.portalsite.Menu</a></li>
-       <li><a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/portalsite/MenuElement.html">org.apache.jetspeed.portalsite.MenuElement</a></li>
-       <li><a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/portalsite/MenuOption.html">org.apache.jetspeed.portalsite.MenuOption</a></li>
-       <li><a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/portalsite/MenuSeparator.html">org.apache.jetspeed.portalsite.MenuSeparator</a></li>
-       <li><a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/portalsite/PortalSiteRequestContext.html">org.apache.jetspeed.portalsite.PortalSiteRequestContext</a></li>
+       <li><a 
href="../apidocs/org/apache/jetspeed/portalsite/Menu.html">org.apache.jetspeed.portalsite.Menu</a></li>
+       <li><a 
href="../apidocs/org/apache/jetspeed/portalsite/MenuElement.html">org.apache.jetspeed.portalsite.MenuElement</a></li>
+       <li><a 
href="../apidocs/org/apache/jetspeed/portalsite/MenuOption.html">org.apache.jetspeed.portalsite.MenuOption</a></li>
+       <li><a 
href="../apidocs/org/apache/jetspeed/portalsite/MenuSeparator.html">org.apache.jetspeed.portalsite.MenuSeparator</a></li>
+       <li><a 
href="../apidocs/org/apache/jetspeed/portalsite/PortalSiteRequestContext.html">org.apache.jetspeed.portalsite.PortalSiteRequestContext</a></li>
 </ul>
-Please refer to the <a 
href="../multiproject/jetspeed-api/apidocs/index.html">javadocs</a> for these 
interfaces and
+Please refer to the <a href="../apidocs/index.html">javadocs</a> for these 
interfaces and
 sample Velocity decorators for more information.
 </p>
 <p>

Modified: 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-user-attributes.xml
URL: 
http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-user-attributes.xml?rev=935850&r1=935849&r2=935850&view=diff
==============================================================================
--- 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-user-attributes.xml
 (original)
+++ 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-deploy/src/site/xdoc/guide-user-attributes.xml
 Tue Apr 20 09:57:11 2010
@@ -64,7 +64,7 @@ String email = (userInfo!=null) ? (Strin
         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/>
+        <a href="../devguide/dev-prefs.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:

Modified: 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/credentials.xml
URL: 
http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/credentials.xml?rev=935850&r1=935849&r2=935850&view=diff
==============================================================================
--- 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/credentials.xml
 (original)
+++ 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/credentials.xml
 Tue Apr 20 09:57:11 2010
@@ -27,24 +27,24 @@
         <section name="Credentials Management Overview">
           <subsection name="DefaultCredentialHandler Features">
             <p>
-                With the Jetspeed <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/DefaultCredentialHandler.html">
+                With the Jetspeed <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/DefaultCredentialHandler.html">
                 <code>DefaultCredentialHandler</code></a> special management 
of password credentials can
                 easily be configured. Through the provided 
-                <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/security/spi/PasswordCredentialProvider.html">
+                <a 
href="../apidocs/org/apache/jetspeed/security/spi/PasswordCredentialProvider.html">
                 <code>PasswordCredentialProvider</code></a> and 
-                <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/security/spi/InternalPasswordCredentialInterceptor.html">
+                <a 
href="../apidocs/org/apache/jetspeed/security/spi/InternalPasswordCredentialInterceptor.html">
                 <code>InternalPasswordCredentialInterceptor</code></a> 
components custom logic can be plugged in for:</p>
             <ul>
                 <li>providing a custom 
-                    <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/security/PasswordCredential.html">
+                    <a 
href="../apidocs/org/apache/jetspeed/security/PasswordCredential.html">
                     <code>PasswordCredential</code></a> implementation</li>
                 <li>password encoding<br/>
                     If an 
-                    <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/security/spi/CredentialPasswordEncoder.html">
+                    <a 
href="../apidocs/org/apache/jetspeed/security/spi/CredentialPasswordEncoder.html">
                     <code>CredentialPasswordEncoder</code></a> is available 
from the 
                     <code>PasswordCredentialProvider</code> passwords will be 
encoded with it before they are persisted.
                     The provided 
-                    <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/MessageDigestCredentialPasswordEncoder.html">
+                    <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/MessageDigestCredentialPasswordEncoder.html">
                     <code>MessageDigestCredentialPasswordEncoder</code></a> 
uses 
                     <a 
href="http://java.sun.com/j2se/1.4.2/docs/api/java/security/MessageDigest.html";>
                     <code>MessageDigest</code></a> hash algorithms for the 
password encryption, and can for example be
@@ -52,24 +52,24 @@
                 </li>
                 <li>enforcing password value rules<br/>
                     If an
-                    <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/security/spi/CredentialPasswordValidator.html">
+                    <a 
href="../apidocs/org/apache/jetspeed/security/spi/CredentialPasswordValidator.html">
                     <code>CredentialPasswordValidator</code></a> is available 
from the
                     <code>PasswordCredentialProvider</code>, passwords will be 
validated with it before they are persisted.
                     The 
-                    <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/DefaultCredentialPasswordValidator.html">
+                    <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/DefaultCredentialPasswordValidator.html">
                     <code>DefaultCredentialPasswordValidator</code></a> for 
example enforces non-emtpy password. And
                     with the 
-                    <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/SimpleCredentialPasswordValidator.html">
+                    <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/SimpleCredentialPasswordValidator.html">
                     <code>SimpleCredentialPasswordValidator</code></a> a 
minimum length and a minum number of numeric
                     characters can be enforced.
                 </li>
                 <li>intercepting 
-                    <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/security/om/InternalCredential.html">
+                    <a 
href="../apidocs/org/apache/jetspeed/security/om/InternalCredential.html">
                     <code>InternalCredential</code></a> lifecycle events<br/>
                     If the <code>DefaultCredentialHandler</code> is provided 
with an
                     <code>InternalPasswordCredentialInterceptor</code>, it 
will invoke this interceptor (or an arbirary
                     set if
-                    <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/InternalPasswordCredentialInterceptorsProxy.html">
+                    <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/InternalPasswordCredentialInterceptorsProxy.html">
                     
<code>InternalPasswordCredentialInterceptorsProxy</code></a> is used) on:
                     <ul>
                       <li>after loading a credential from the persistent 
store</li>
@@ -80,14 +80,14 @@
                     Jetspeed already provides a basic set of interceptors, 
ready to be used:
                     <ul>
                       <li>
-                          <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/ValidatePasswordOnLoadInterceptor.html">
+                          <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/ValidatePasswordOnLoadInterceptor.html">
                           
<code>ValidatePasswordOnLoadInterceptor</code></a><br/>
                           This interceptor can be used to validate (pre)set 
passwords in the persistent store and force
                           a required change by the user if invalid. It uses 
the configured <code>CredentialPasswordValidator</code>
                           of the <code>PasswordCredentialProvider</code>, the 
same as used when a password is changed.
                       </li>
                       <li>
-                          <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/EncodePasswordOnFirstLoadInterceptor.html">
+                          <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/EncodePasswordOnFirstLoadInterceptor.html">
                           
<code>EncodePasswordOnFirstLoadInterceptor</code></a><br/>
                           This interceptor can be used if passwords needs to 
be preset in the persistent store or
                           migrated unencoded from a different store. With this 
interceptor, these cleartext password
@@ -95,7 +95,7 @@
                           <code>CredentialPasswordEncoder</code> from the 
<code>PasswordCredentialProvider</code>
                       </li>
                       <li>
-                          <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/PasswordExpirationInterceptor.html">
+                          <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/PasswordExpirationInterceptor.html">
                           <code>PasswordExpirationInterceptor</code></a><br/>
                           This interceptor can be used to enforce a maximum 
lifespan for passwords.
                           It manages the <code>expiration_date</code> and 
<code>is_expired</code> members of the
@@ -106,7 +106,7 @@
                           expiration (described further below). 
                       </li>
                       <li>
-                          <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/MaxPasswordAuthenticationFailuresInterceptor.html">
+                          <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/MaxPasswordAuthenticationFailuresInterceptor.html">
                           
<code>MaxPasswordAuthenticationFailuresInterceptor</code></a><br/>
                           This interceptor can be used to prevent password 
hacking by enforcing a maximum number of
                           invalid password attempts in a row. Once this number 
of authentication failures is reached,
@@ -114,13 +114,13 @@
                           will automatically be reset to zero again by the 
<code>DefaultCredentialHandler</code>.
                       </li>                          
                       <li>
-                          <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/PasswordHistoryInterceptor.html">
+                          <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/PasswordHistoryInterceptor.html">
                           <code>PasswordHistoryInterceptor</code></a><br/>
                           This interceptor can be used to enforce usage of 
unique new passwords in respect to a certain
                           number of previous used passwords. When a new 
password is set, the current password is saved
                           in a FIFO stack of used passwords. When a user 
itself changes its password, it must be different
                           from all the onces thus saved, otherwise a 
-                          <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/security/PasswordAlreadyUsedException.html">
+                          <a 
href="../apidocs/org/apache/jetspeed/security/PasswordAlreadyUsedException.html">
                           <code>PasswordAlreadyUsedException</code></a> will be
                           thrown. But setting a new password through the 
administrative interface still allows any
                           password (when otherwise valid) to be set.
@@ -129,7 +129,7 @@
                     <p>
                     The <code>DefaultCredentialHandler</code> only supports 
one interceptor to be configured.
                     But, with the 
-                        <a 
href="../multiproject/jetspeed-security/apidocs/org/apache/jetspeed/security/spi/impl/InternalPasswordCredentialInterceptorsProxy.html">
+                        <a 
href="../apidocs/org/apache/jetspeed/security/spi/impl/InternalPasswordCredentialInterceptorsProxy.html">
                     
<code>InternalPasswordCredentialInterceptorsProxy</code></a>, a list of 
interceptors can
                     be configured which then will be invoked sequentially.</p>
                     <p>

Modified: 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-database.xml
URL: 
http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-database.xml?rev=935850&r1=935849&r2=935850&view=diff
==============================================================================
--- 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-database.xml
 (original)
+++ 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-database.xml
 Tue Apr 20 09:57:11 2010
@@ -264,7 +264,7 @@ org.apache.jetspeed.production.jdbc.driv
                        <subsection name="Datasource Configuration with 
Jetspeed-2">
                        <p>
                        Jetspeed-2 requires a datasource to be configured in 
the application server on which it is being deployed.
-                       For more information, see the <a 
href="../multiproject/jetspeed-rdbms/index.html">RDBMS component 
documentation</a>.
+                       For more information, see the <a 
href="dev-rdbms.html">RDBMS component documentation</a>.
                        </p>
                        </subsection>
 

Modified: 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-decorators.xml
URL: 
http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-decorators.xml?rev=935850&r1=935849&r2=935850&view=diff
==============================================================================
--- 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-decorators.xml
 (original)
+++ 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-decorators.xml
 Tue Apr 20 09:57:11 2010
@@ -179,7 +179,7 @@ approaches described here can be applied
                <br/><br/>
             Next up we have this line <code>#set($rootFragment = 
$jetspeed.currentFragment)</code> another set()
             statement, this time creating an object called 
<code>$rootFragment</code> which is an instance of
-            <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/om/page/ContentFragment.html">org.apache.jetspeed.om.page.ContentFragment</a>.
+            <a 
href="../apidocs/org/apache/jetspeed/om/page/ContentFragment.html">org.apache.jetspeed.om.page.ContentFragment</a>.
                        It is really not relevant to this guide
             to describe what <code>$jetspeed.currentFragment</code> is doing 
so I am going to skip that and move on. 
             <br/><br/>
@@ -191,9 +191,9 @@ approaches described here can be applied
             <br/>
             Ah <code>$request</code>, now that looks familiar, this is 
actually an instance of <code>javax.servlet.http.HttpServletRequest</code>
             from which we are retreiving objects that were been placed into 
Velocity by Jetspeed.  The actual objects are:
-            <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/portalsite/PortalSiteRequestContext.html">org.apache.jetspeed.portalsite.PortalSiteRequestContext</a>
+            <a 
href="../apidocs/org/apache/jetspeed/portalsite/PortalSiteRequestContext.html">org.apache.jetspeed.portalsite.PortalSiteRequestContext</a>
             and
-            <a 
href="../multiproject/jetspeed-api/apidocs/org/apache/jetspeed/decoration/Theme.html">org.apache.jetspeed.decoration.Theme</a>
+            <a 
href="../apidocs/org/apache/jetspeed/decoration/Theme.html">org.apache.jetspeed.decoration.Theme</a>
             respectively.  We will put all of these objects to good use in 
just a little while.       
         </p>
          <h4>Feed Your HEAD: How to Properly Code Your Head Tag.</h4>

Modified: 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-portlet-bridges.xml
URL: 
http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-portlet-bridges.xml?rev=935850&r1=935849&r2=935850&view=diff
==============================================================================
--- 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-portlet-bridges.xml
 (original)
+++ 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-portlet-bridges.xml
 Tue Apr 20 09:57:11 2010
@@ -57,12 +57,6 @@ The Portals Bridges project provides a P
 Please visit the <a 
href="http://portals.apache.org/bridges/multiproject/portals-bridges-velocity/index.html";>Apache
 Portals Velocity Portlet Bridge</a>
 sub project documentation.
 </p>
-<p>
-An example of the Velocity Bridge usage within Jetspeed 2 is:
-<ul>
-    <li>The Jetspeed 2 <a 
href="../multiproject/j2-admin/index.html">Administration and Security</a> 
application</li>
-</ul>
-</p>
 </section>
 
 <section name="Perl Portlet Bridge">

Modified: 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-simple-velocity-portlet.xml
URL: 
http://svn.apache.org/viewvc/portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-simple-velocity-portlet.xml?rev=935850&r1=935849&r2=935850&view=diff
==============================================================================
--- 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-simple-velocity-portlet.xml
 (original)
+++ 
portals/site/jetspeed/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/guide-simple-velocity-portlet.xml
 Tue Apr 20 09:57:11 2010
@@ -114,7 +114,7 @@ javac -cp portlet-api-1.0.jar:portals-br
                         whatever content
                         you desire in it. Notice that the template file is 
defined in the portlet init
                         parameter <code>
-                        ViewPage</code>. The objects <a 
href="http://portals.apache.org/pluto/multiproject/portlet-api/apidocs/javax/portlet/PortletConfig.html";>PortletConfig</a>,
 <a 
href="http://portals.apache.org/pluto/multiproject/portlet-api/apidocs/javax/portlet/RenderRequest.html";>RenderRequest</a>,
 and <a 
href="http://portals.apache.org/pluto/multiproject/portlet-api/apidocs/javax/portlet/RenderResponse.html";>RenderResponse</a>
+                        ViewPage</code>. The objects <a 
href="http://portals.apache.org/pluto/portlet-2.0-apidocs/javax/portlet/PortletConfig.html";>PortletConfig</a>,
 <a 
href="http://portals.apache.org/pluto/portlet-2.0-apidocs/javax/portlet/RenderRequest.html";>RenderRequest</a>,
 and <a 
href="http://portals.apache.org/pluto/portlet-2.0-apidocs/javax/portlet/RenderResponse.html";>RenderResponse</a>
                         are automatically
                         placed in the Velocity context for use in Velocity 
templates. Here is a sample
                         template showing a few of these objects methods and 
properties.


Reply via email to