portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From woon...@apache.org
Subject svn commit: r722827 [2/2] - in /portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site: resources/images/components/ resources/images/components/ldap/ resources/images/guides/ resources/images/guides/profiler/ xdoc/components/jetspeed-ca...
Date Wed, 03 Dec 2008 09:53:25 GMT
Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/arch.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/arch.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/arch.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/arch.xml
Wed Dec  3 01:53:22 2008
@@ -42,7 +42,7 @@
                 The following diagram describes the high level security architecture:
             </p>
             <p align="center">
-                <img src="images/arch-overview.gif" border="0" />
+                <img src="../../images/components/arch-overview.gif" border="0" />
             </p>
             <p>
                 Configuration files for each component areas are specified.  For more information,
go to the documentation

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atn-spi.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atn-spi.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atn-spi.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atn-spi.xml
Wed Dec  3 01:53:22 2008
@@ -36,7 +36,7 @@
                 .
             </p>
             <p>
-                <img src="images/atn-spi-arch-c.gif" border="0" />
+                <img src="../../images/components/atn-spi-arch-c.gif" border="0" />
             </p>
         </section>
         <section name="Authentication SPI Components">

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atn.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atn.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atn.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atn.xml
Wed Dec  3 01:53:22 2008
@@ -35,7 +35,7 @@
                 the <a href="atn-spi.html">Authentication SPI</a> to interact
with various implementation and user stores.
             </p>
             <p>
-                <img src="images/atn-arch-c.gif" border="0" />
+                <img src="../../images/components/atn-arch-c.gif" border="0" />
             </p>
             <p>
                 The various components described above fulfill the following functions:

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz-jaas.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz-jaas.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz-jaas.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz-jaas.xml
Wed Dec  3 01:53:22 2008
@@ -124,7 +124,7 @@
                 .
             </p>
             <p>
-                <img src="images/rdbms-policy-c.gif" border="0" />
+                <img src="../../images/components/rdbms-policy-c.gif" border="0" />
             </p>
             <p>
                 To get more detail about the implementation of the

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz-spi.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz-spi.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz-spi.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz-spi.xml
Wed Dec  3 01:53:22 2008
@@ -39,13 +39,13 @@
             </p>
             <p>First, let's have a look at a class diagram of the authorization SPI:</p>
             <p>
-                <img src="images/security-mapping-c.gif" border="0" />
+                <img src="../../images/components/security-mapping-c.gif" border="0" />
                 <br />
                 <br />
-                <img src="images/role-security-handler-c.gif" border="0" />
+                <img src="../../images/components/role-security-handler-c.gif" border="0"
/>
                 <br />
                 <br />
-                <img src="images/group-security-handler-c.gif" border="0" />
+                <img src="../../images/components/group-security-handler-c.gif" border="0"
/>
                 <br />
                 <br />
             </p>

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/atz.xml
Wed Dec  3 01:53:22 2008
@@ -30,7 +30,7 @@
                 a relation database store to manage associations between principals and permissions.
             </p>
             <p align="center">
-                <img src="images/rdbms-policy-overview-c.gif" border="0" />
+                <img src="../../images/components/rdbms-policy-overview-c.gif" border="0"
/>
             </p>
             <p>
                 The <code>PermissionManager</code> provides access to the permissions
associated to given principals.

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/credentials.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/credentials.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/credentials.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/credentials.xml
Wed Dec  3 01:53:22 2008
@@ -149,7 +149,7 @@
                 implementation.
             </p>
             <p align="center">
-                <img src="images/credential-handler-c.gif" border="0" />
+                <img src="../../images/components/credential-handler-c.gif" border="0"
/>
             </p>
             <p>
                 The OJB mappings for the default credentials implementation are described
in 
@@ -160,7 +160,7 @@
                 The following database schema is used to stored credentials and their associations
to principals.
             </p>
             <p align="center">
-                <img src="images/principals-credentials-schema.gif" border="0" />
+                <img src="../../images/components/principals-credentials-schema.gif" border="0"
/>
             </p>
           </subsection>
         </section>
@@ -262,7 +262,7 @@
               For this to work, a <code>"security"</code> Profiler rule must
have been setup like the default one 
               provided by Jetspeed:</p>
               <p align="center">
-                <img src="images/security-locator.jpg" border="0"/>
+                <img src="../../images/components/security-locator.jpg" border="0"/>
               </p>
               <p>
               As can seen from the above image, the default page which will be presented
to the user is the
@@ -296,7 +296,7 @@
               If enabled, this portlet can display the current expiration date of a password
and also allows to change
               its value:</p>
               <p align="center">
-                <img src="images/password-expiration.jpg" border="0"/>
+                <img src="../../images/components/password-expiration.jpg" border="0"/>
               </p>              
               <p>
               As you can see, through the radio group, the password expiration date can be
changed to:</p>
@@ -312,7 +312,7 @@
               <p>
               This feature can be enabled through the edit/preferences page of the <code>UserDetailsPortlet</code>:</p>
               <p align="center">
-                <img src="images/user-detail-prefs.jpg" border="0"/>
+                <img src="../../images/components/user-detail-prefs.jpg" border="0"/>
               </p>
               <p>
               Note: when a new password value is specified selected password expiration action
<code>Expired</code>
@@ -328,7 +328,7 @@
               <p>
               With the preferences set as in the example shown above, the <code>Add
User</code> dialog will look like this:</p>
               <p align="center">
-                <img src="images/add-user.jpg" border="0"/>
+                <img src="../../images/components/add-user.jpg" border="0"/>
               </p>
               <p>
               A user added with the example preferences set, will have the <code>updateRequired</code>
property set to

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/index.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/index.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/index.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/index.xml
Wed Dec  3 01:53:22 2008
@@ -66,7 +66,7 @@
                 as its default IoC container.
             </p>
             <p>
-                <img src="images/components.jpg" align="right" border="0" hspace="1" vspace="2"
/>
+                <img src="../../images/components/components.jpg" align="right" border="0"
hspace="1" vspace="2" />
                 Jetspeed 2 security services are founded on a set of modular and extensible
security modules exposed through an SPI model. The SPI model
                 provides the ability to modify the behavior of the Jetspeed coarsed security
services (UserManager, RoleManager, GroupManager)
                 through the modification and configuration of specialized handlers. For

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/ldap.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/ldap.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/ldap.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/ldap.xml
Wed Dec  3 01:53:22 2008
@@ -816,7 +816,7 @@
         </p>
         
         <p>Validate the connection using an LDAP browser:</p>
-        <p align="center"><img src="images/ldap/rootPassword.png" border="0"/></p>
       
+        <p align="center"><img src="../../images/components/ldap/rootPassword.png"
border="0"/></p>        
         <br/>        
       </subsection>
       <subsection name="LDAP Object Filters">
@@ -957,7 +957,7 @@
          </p>
          <p>The role contains a member attribute, listing all users belonging to that
role.</p>
          <p align="center">
-           <img src="images/ldap/RoleMembershipAttributes1.png" border="0"/><br/>
+           <img src="../../images/components/ldap/RoleMembershipAttributes1.png" border="0"/><br/>
            <i>A role with 2 members</i>
          </p>
          <br/>
@@ -965,7 +965,7 @@
            The value of the member attribute is the fully qualified DN of the user (including
the root context). As you can see, the user doesn't contain any attributes with regards to
role membership.
          </p>
          <p align="center">
-           <img src="images/ldap/RoleMembershipAttributes2.png" border="0"/><br/>
+           <img src="../../images/components/ldap/RoleMembershipAttributes2.png" border="0"/><br/>
            <i>A user</i>
          </p>
          <br/>
@@ -995,7 +995,7 @@
           This will make sure that for each role the user belongs to, the memberOf attribute
is set on the user object, as can be seen in the following screenshot:
         </p>
          <p align="center">
-           <img src="images/ldap/UserRoleMembershipAttributes1.png" border="0"/><br/>
+           <img src="../../images/components/ldap/UserRoleMembershipAttributes1.png" border="0"/><br/>
            <i>User belonging to 4 different roles</i>
          </p>
          <br/>
@@ -1019,7 +1019,7 @@
           This is configurable by Jetspeed through the <b>RequiredAttributeClasses</b>
property.
          </p>         
          <p align="center">
-           <img src="images/ldap/UserRoleMembershipAttributes2.png" border="0"/><br/>
+           <img src="../../images/components/ldap/UserRoleMembershipAttributes2.png" border="0"/><br/>
            <i>A role without any members</i>
          </p>
          <br/>
@@ -1053,7 +1053,7 @@
           In the previous example, the <b>GroupMembershipAttributes</b> was blank,
so instead the <b>UserGroupMembershipAttributes</b> was used on the user level:
         </p>
          <p align="center">
-           <img src="images/ldap/GroupMembershipAttributes1.png" border="0"/><br/>
+           <img src="../../images/components/ldap/GroupMembershipAttributes1.png" border="0"/><br/>
          </p>
          <br/>
          <p>
@@ -1061,7 +1061,7 @@
            As you can see, the user doesn’t contain any attributes with regards to group
membership.
          </p>
          <p align="center">
-           <img src="images/ldap/GroupMembershipAttributes2.png" border="0"/><br/>
+           <img src="../../images/components/ldap/GroupMembershipAttributes2.png" border="0"/><br/>
          </p>
          
        <br/>
@@ -1081,7 +1081,7 @@
           Only one of those parameters can be filled in. If the <b>GroupMemberShipAttributes</b>
is set, Jetspeed assumes that the attribute to determine group membership is on the group
object.
         </p>
          <p align="center">
-           <img src="images/ldap/UserGroupMembershipAttributes1.png" border="0"/><br/>
+           <img src="../../images/components/ldap/UserGroupMembershipAttributes1.png"
border="0"/><br/>
            <i>User belonging to 2 different roles</i>
          </p>
          <br/>
@@ -1093,7 +1093,7 @@
            As you can see, the role is defined in <b>cn=role1,o=sevenSeas</b>.
(notice the empty uniqueMember attribute).
          </p>
          <p align="center">
-           <img src="images/ldap/UserGroupMembershipAttributes2.png" border="0"/><br/>
+           <img src="../../images/components/ldap/UserGroupMembershipAttributes2.png"
border="0"/><br/>
            <i>Role definition</i>
          </p>
          <br/>
@@ -1128,7 +1128,7 @@
           In the previous example, the GroupMembershipAttributes was blank, so instead the
UserGroupMembershipAttributes was used on the user level.
         </p>
          <p align="center">
-           <img src="images/ldap/GroupMembershipForRoleAttributes1.png" border="0"/><br/>
+           <img src="../../images/components/ldap/GroupMembershipForRoleAttributes1.png"
border="0"/><br/>
          </p>
          <br/>
          <p>
@@ -1136,7 +1136,7 @@
            As you can see, the user doesn’t contain any attributes with regards to group
membership.
         </p>
          <p align="center">
-           <img src="images/ldap/GroupMembershipForRoleAttributes2.png" border="0"/><br/>
+           <img src="../../images/components/ldap/GroupMembershipForRoleAttributes2.png"
border="0"/><br/>
          </p>
 
        <br/>
@@ -1153,7 +1153,7 @@
           This will make sure that the <b>memberOf</b> attribute is set on the
user object, as can be seen in the following screenshot.
         </p>
          <p align="center">
-           <img src="images/ldap/GroupMembershipForRoleAttributes1.png" border="0"/><br/>
+           <img src="../../images/components/ldap/GroupMembershipForRoleAttributes1.png"
border="0"/><br/>
          </p>
          <br/>
          <p>
@@ -1161,14 +1161,14 @@
            As you can see, the user doesn’t contain any attributes with regards to group
membership.
         </p>
          <p align="center">
-           <img src="images/ldap/GroupMembershipForRoleAttributes2.png" border="0"/><br/>
+           <img src="../../images/components/ldap/GroupMembershipForRoleAttributes2.png"
border="0"/><br/>
          </p>
          <br/>
          <p>
            Only one of those parameters can be filled in. If the <b>GroupMemberShipAttributes</b>
is set, Jetspeed assumes that the attribute to determine group membership is on the group
object.
          </p>
          <p align="center">
-           <img src="images/ldap/RoleGroupMembershipForRoleAttributes1.png" border="0"/><br/>
+           <img src="../../images/components/ldap/RoleGroupMembershipForRoleAttributes1.png"
border="0"/><br/>
            <i>User belonging to 2 different roles</i>
          </p>
          <br/>
@@ -1178,7 +1178,7 @@
          </p>
          <p>As you can see, the role is defined in <b>cn=role1,o=sevenSeas</b>.
(notice the empty uniqueMember attribute).</p>
          <p align="center">
-           <img src="images/ldap/RoleGroupMembershipForRoleAttributes2.png" border="0"/><br/>
+           <img src="../../images/components/ldap/RoleGroupMembershipForRoleAttributes2.png"
border="0"/><br/>
            <i>Role definition</i>
          </p>
          <br/>
@@ -1209,7 +1209,7 @@
           Jetspeed will limit its search scope on the LDAP to the property values defined
above. This means that only roles, groups and people within rootOrg will be used by Jetspeed.
         </p>
         <p align="center">
-          <img src="images/ldap/ObjectFilterBase.png" border="0"/><br/>
+          <img src="../../images/components/ldap/ObjectFilterBase.png" border="0"/><br/>
         </p>
         <br/>
         <p>So, together with the object filers (RoleFilter, GroupFilter, UserFilter),
Jetspeed will be able to locate the roles, groups and users within the directory.</p>
@@ -1225,7 +1225,7 @@
 </constructor-arg>]]></source>
         </p>
         <p align="center">
-          <img src="images/ldap/RoleFilterBase.png" border="0"/><br/>
+          <img src="../../images/components/ldap/RoleFilterBase.png" border="0"/><br/>
         </p>
 
        <br/>
@@ -1238,7 +1238,7 @@
 </constructor-arg>]]></source>
         </p>
         <p align="center">
-          <img src="images/ldap/GroupFilterBase.png" border="0"/><br/>
+          <img src="../../images/components/ldap/GroupFilterBase.png" border="0"/><br/>
         </p>
         
        <br/>
@@ -1251,7 +1251,7 @@
 </constructor-arg>]]></source>
         </p>
         <p align="center">
-          <img src="images/ldap/UserFilterBase.png" border="0"/><br/>
+          <img src="../../images/components/ldap/UserFilterBase.png" border="0"/><br/>
         </p>
         
       </subsection>
@@ -1281,7 +1281,7 @@
         </p>
         <p>Using the settings above, roles will be created like this</p>
         <p align="center">
-          <img src="images/ldap/RoleObjectClasses.png" border="0"/><br/>
+          <img src="../../images/components/ldap/RoleObjectClasses.png" border="0"/><br/>
         </p>
         <p>Notice how all of the objectClasses defined by the RoleObjectClasses attribute
have been created in the LDAP</p>
         
@@ -1295,7 +1295,7 @@
         </p>
         <p>Using the settings above, groups will be created like this</p>
         <p align="center">
-          <img src="images/ldap/GroupObjectClasses.png" border="0"/><br/>
+          <img src="../../images/components/ldap/GroupObjectClasses.png" border="0"/><br/>
         </p>
         <p>Notice how all of the objectClasses defined by the GroupObjectClasses attribute
have been created in the LDAP</p>
         
@@ -1309,7 +1309,7 @@
         </p>
         <p>Using the settings above users will be created like this</p>
         <p align="center">
-          <img src="images/ldap/UserObjectClasses.png" border="0"/><br/>
+          <img src="../../images/components/ldap/UserObjectClasses.png" border="0"/><br/>
         </p>
         <p>Notice how all of the objectClasses defined by the UserObjectClasses attribute
have been created in the LDAP</p>
         
@@ -1333,7 +1333,7 @@
         <p><b>cn</b> is the naming attribute for the user object, as no
2 admin users can exist in the rootOrg/People subdirectory</p>
         
         <p align="center">
-          <img src="images/ldap/IdAttributes.png" border="0"/><br/>
+          <img src="../../images/components/ldap/IdAttributes.png" border="0"/><br/>
         </p>
         <br/>
         
@@ -1367,7 +1367,7 @@
         </p>
         <p>In the screenshot below, users have the <b>uid</b> attribute
as their naming attribute</p>
         <p align="center">
-          <img src="images/ldap/UserIdAttribute.png" border="0"/><br/>
+          <img src="../../images/components/ldap/UserIdAttribute.png" border="0"/><br/>
         </p>
         
       </subsection>
@@ -1381,7 +1381,7 @@
         
         <p>When Jetspeed builds a userPrincipal internally, it will use the attribute
corresponding to the value of the userUidAttribute.</p>
         <p align="center">
-          <img src="images/ldap/userUidAttribute.png" border="0"/><br/>
+          <img src="../../images/components/ldap/userUidAttribute.png" border="0"/><br/>
         </p>
 
        <br/>

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/login-module.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/login-module.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/login-module.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/login-module.xml
Wed Dec  3 01:53:22 2008
@@ -87,7 +87,7 @@
             <table>
                 <tr>
                     <td style="background-color:#FFFFFF;" align="center">
-                        <img src="images/default-login-module-c.gif" border="0" />
+                        <img src="../../images/components/default-login-module-c.gif"
border="0" />
                     </td>
                 </tr>
             </table>

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/permission.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/permission.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/permission.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-security/permission.xml
Wed Dec  3 01:53:22 2008
@@ -36,14 +36,14 @@
             to the <code>PermissionManager</code>.
             </p>
             <p>
-            <img src="images/permission-mgr-c.gif" border="0" />
+            <img src="../../images/components/permission-mgr-c.gif" border="0" />
             </p>
             <p>
             Each <code>InternalPermission</code> maps to one or more <code>InternalPrincipal</code>
and, each 
             <code>InternalPrincipal</code> can have one or more <code>InternalPermission</code>.
             </p>
             <p>
-            <img src="images/permissions-principals-om-c.gif" border="0" />
+            <img src="../../images/components/permissions-principals-om-c.gif" border="0"
/>
             </p>
         </section>
         <section name="Schema and OJB Mapping">
@@ -74,7 +74,7 @@
             The relational schema maintaining principal to permission associations is provided
below:
             </p>
             <p>
-            <img src="images/permissions-principals-schema.gif" border="0" />
+            <img src="../../images/components/permissions-principals-schema.gif" border="0"
/>
             </p>
         </section>
     </body>

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-sso/index.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-sso/index.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-sso/index.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-sso/index.xml
Wed Dec  3 01:53:22 2008
@@ -43,7 +43,7 @@
 <table>
                 <tr>
                     <td style="background-color:#FFFFFF;" align="center">
-                        <img src="images/sso-manage.gif" border="0" />
+                        <img src="../../images/components/sso-manage.gif" border="0" />
                     </td>
                 </tr>
             </table>

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/aggregation.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/aggregation.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/aggregation.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/aggregation.xml
Wed Dec  3 01:53:22 2008
@@ -35,7 +35,7 @@
     AggregateStatistics queryStatistics(StatisticsQueryCriteria criteria)</source>
     		The <code>AggregateStatistics</code> can then be used for reporting purpose.
             <br/>
-        	<img src="images/aggregatestatistics-c.gif" border="0" />
+        	<img src="../../images/components/aggregatestatistics-c.gif" border="0" />
 			</p>
 			</subsection>
 			<subsection name="Using Aggregate Statistics">

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/index.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/index.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/index.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/index.xml
Wed Dec  3 01:53:22 2008
@@ -52,20 +52,20 @@
 			<li><b>%b </b>- number of bytes sent (&quot;-&quot; if no bytes
sent).</li>
 			</ul>
         	<br/>
-        	<img src="images/portalstatistics-c.gif" border="0" />
+        	<img src="../../images/components/portalstatistics-c.gif" border="0" />
         	</p>
         	<p>
         	Statistics data is stored in 3 relational tables as illustrated below:
         	<br/><br/>
-        	<img src="images/statistics-db.gif" border="0" />
+        	<img src="../../images/components/statistics-db.gif" border="0" />
         	</p>
         	<p>
         	Each event type is mapped to a data holder that gets persisted in the statistics
tables illustrated above.
-        	<img src="images/logrecord-c.gif" border="0" />
+        	<img src="../../images/components/logrecord-c.gif" border="0" />
         	<br/>
         	Jetspeed-2 persists the collected data in batches through the <code>BatchedStatistics</code>
component.
         	<br/><br/>
-        	<img src="images/batchedstatistics-c.gif" border="0" />
+        	<img src="../../images/components/batchedstatistics-c.gif" border="0" />
         	</p>
         	</subsection>
         	<subsection name="PortalStatistics Configuration">

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/stats.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/stats.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/stats.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/components/jetspeed-statistics/stats.xml
Wed Dec  3 01:53:22 2008
@@ -45,8 +45,8 @@
     		<p>
     		Jetpseed-2 provides administrative portlets that report on portal statistics.
     		<br/><br/>
-    		<img src="images/portlet-statistics.gif" border="0"/><br/>
-    		<img src="images/page-statistics.gif" border="0"/>
+    		<img src="../../images/components/portlet-statistics.gif" border="0"/><br/>
+    		<img src="../../images/components/page-statistics.gif" border="0"/>
     		</p>
     		</subsection>
 		</section>

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-components.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-components.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-components.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-components.xml
Wed Dec  3 01:53:22 2008
@@ -52,7 +52,7 @@
 		</p>
 		<p>
 		Jetspeed-2 component framework assembly is configured and implemented in <i>JetspeedServlet</i>:<br/><br/>
-		<img src="images/jetspeedservlet-c.gif" border="0"/>
+		<img src="../images/guides/jetspeedservlet-c.gif" border="0"/>
 		</p>
 		<p>
 		The <code>JetspeedServlet</code> is configured in the portal application <i>web.xml</i>
to load at startup.  The <code>initializeComponentManager</code>

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-desktop.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-desktop.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-desktop.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-desktop.xml
Wed Dec  3 01:53:22 2008
@@ -522,7 +522,7 @@
 (Fusion) to give JSR168 support to Jetspeed 1.6 portals.
 </p> 
 <p>Here is an example of "just the content" of a portlet without window decorations:</p>
-<img src="images/portlet-pipeline.png"/>
+<img src="../images/guides/portlet-pipeline.png"/>
 </subsection>
 <subsection name="Portal Pipeline">
 <p>Portal pipeline uses a server-side aggregation engine. All 
@@ -563,7 +563,7 @@
  </fragment> 
 ]]></source>   
 <p>Here is a view of the above fragments in the desktop customizer:</p>			
-<img src="images/desktop-layout.png"/>
+<img src="../images/guides/desktop-layout.png"/>
 </section>
 </body>
 </document>

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-j2-development.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-j2-development.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-j2-development.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-j2-development.xml
Wed Dec  3 01:53:22 2008
@@ -36,7 +36,7 @@
 			When working with Eclipse with the <a href="http://subclipse.tigris.org/">Subclipse
plugin</a>,
 			it is possible to generate a patch for the code changed as illustrated below:
 			<br/><br/>
-			<img src="images/create-patch.gif" border="0" />
+			<img src="../images/guides/create-patch.gif" border="0" />
 			</p>
 			</subsection>
 		</section>

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-layouts.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-layouts.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-layouts.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-layouts.xml
Wed Dec  3 01:53:22 2008
@@ -52,7 +52,7 @@
 </ul>
 </p>
 <p>
-    <img src='images/layouts/layouts-overview.png'/>
+    <img src='../images/layouts/layouts-overview.png'/>
 </p>
 </section>
 <section name="Layouts Packaging">

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-pipeline.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-pipeline.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-pipeline.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-pipeline.xml
Wed Dec  3 01:53:22 2008
@@ -27,7 +27,7 @@
 		<section name="Jetspeed-2 Pipeline">
 			<p>As described below, one of key component of the Jetspeed-2 portal engine is its
request pipeline.
 			<br/><br/>
-			<img src="images/j2-overview.gif" border="0"/>
+			<img src="../images/guides/j2-overview.gif" border="0"/>
 			<br/>
 			In Jetspeed-2 request are processed through a series of <code>Valve</code>
assembled together as a
 			pipeline.  For detailed information about Jetspeed-2 pipeline, 

Modified: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-profiler.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-profiler.xml?rev=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-profiler.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-profiler.xml
Wed Dec  3 01:53:22 2008
@@ -46,7 +46,7 @@
 Jetspeed comes with quite a few predefined rules for taking criteria from request parameters,
HTTP headers,
 security information, language and session attributes. The profiler is invoked during the
Jetspeed request 
 processing pipeline in the profiler valve. 
-<img src="images/profiler/profiler-pipeline.jpg" border="1"/>   
+<img src="../images/guides/profiler/profiler-pipeline.jpg" border="1"/>   
 </p>
 <p>  
 All of these runtime parameters are called the <i>profile criterion</i>, which
the profiler uses to locate 
@@ -87,7 +87,7 @@
         <td>contains complete subsite trees, exactly like root tree</td>
     </tr>    
 </table>        
-<img src="images/profiler/pages.jpg" border="1"/>           
+<img src="../images/guides/profiler/pages.jpg" border="1"/>           
 </p>    
 <p>By applying profiling rules, the profiler locates pages in the portal site directory.</p>
 </section>      
@@ -550,13 +550,13 @@
 pages, folders, menus and links. A locator contains a collection of properties 
 (name value pairs) describing the actual resource to be located. 
 </p>
-<img src="images/profiler/parameter-resolution.jpg" border="1"/>           
+<img src="../images/guides/profiler/parameter-resolution.jpg" border="1"/>        
  
 <p>
 The profiler takes runtime information as input, generalized into 
 generalized profile locators that are passed on to the page manager to locate a  page or
menu. 
 The profile locators are normalized and not coupled to the profiler or page manager implementation.
 </p>       
-<img src="images/profiler/parameter-resolution-2.jpg" border="1"/>               
+<img src="../images/guides/profiler/parameter-resolution-2.jpg" border="1"/>      
        
 </section>
 <section name='Principal Rules'>
 <p>Each user principal can be mapped to specific profiling rule. This association is
stored in the Jetspeed database.
@@ -567,7 +567,7 @@
 has a tab for editing user profile information:
 </p>
 <p>    
-<img src="images/profiler/user-profile-locator.jpg" border="1"/>               
+<img src="../images/guides/profiler/user-profile-locator.jpg" border="1"/>        
      
 </p>
 <p>
 Often, profiling rules are determined and then associated by portal-specific logic during
user registration (or self-registration).    

Modified: 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=722827&r1=722826&r2=722827&view=diff
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-subsites.xml
(original)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/guides/guide-subsites.xml
Wed Dec  3 01:53:22 2008
@@ -46,7 +46,7 @@
         </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"/>
+        <img src='../images/guides/subsites2.jpg' border="0"/>
         <p>Here we have three subsites (four including localhost) defined for three
different companies:
         </p>
         <ul>
@@ -57,7 +57,7 @@
         </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"/>        
+        <img src='../images/guides/subsites.jpg' border="0"/>        
         <p>Here we have three subsites (four including localhost) defined for three
different companies:
         </p>
         <ul>
@@ -181,7 +181,7 @@
 <p>
 The screenshot below shows the directory tree for a <i>localhost</i> subsite.
 </p>
-<img src='images/localhost-site.jpg'/>
+<img src='../images/guides/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.
@@ -240,7 +240,7 @@
 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"/>
+<img src='../images/guides/user-profile.jpg' border="0"/>
 <p>
 Additionally, you can associate users with profiling rules in the XML seed data configuration:
 </p>
@@ -316,12 +316,12 @@
         	<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"/>        
+        <img src='../images/guides/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"/>                        	
       	
+        <img src='../images/guides/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:
@@ -330,7 +330,7 @@
         	<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"/>                       
	
+        <img src='../images/guides/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:



---------------------------------------------------------------------
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