You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@portals.apache.org by ta...@apache.org on 2009/04/26 05:36:56 UTC
svn commit: r768636 [19/25] - in /portals/site: jetspeed-2.1/ jetspeed-2.2/
jetspeed-2.2/jetspeed-guide-admin/ jetspeed-2.2/jetspeed-guide-admin/src/
jetspeed-2.2/jetspeed-guide-admin/src/site/
jetspeed-2.2/jetspeed-guide-admin/src/site/resources/ jets...
Added: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/j2-maven-plugin.xml
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/j2-maven-plugin.xml?rev=768636&view=auto
==============================================================================
--- portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/j2-maven-plugin.xml (added)
+++ portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/j2-maven-plugin.xml Sun Apr 26 03:36:40 2009
@@ -0,0 +1,535 @@
+<?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 Maven Plugin</title>
+ <subtitle>Documentation for Using Jetspeed 2 Maven Plugin</subtitle>
+ <authors>
+ <person name="David Le Strat" email="dlestrat@apache.org" />
+ <person name="Ate Douma" email="ate@douma.nu" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Maven-2 Plugin Overview">
+ <p>
+ Adding functionality to Maven is done through the Maven plugin mechanism. Maven comes shipped with numerous
+ plugins and provides an extensible framework for writing custom plugins.
+ Details on custom Maven plugins can be found in the
+ <a href="http://maven.apache.org/guides/plugin/guide-java-plugin-development.html">Writing a Plugin</a> section of Maven's web
+ site.
+ </p>
+ <p>
+ Jetspeed 2 has developed a custom Maven plugin that centralizes most common build goals required to build a
+ Jetspeed 2 based portal application. This provides many benefits:
+ </p>
+ <ul>
+ <li>
+ Better reusability of common build goals. Developers creating a new portal application can leverage the
+ Jetspeed 2 Maven plugin for common build operations.
+ </li>
+ <li>
+ The ability to quickly get started with a portal application. With the goal <code>j2:portal.genapp</code>
+ a new portal application can be created. The developer of the new application can reuse the Jetspeed 2
+ Maven plugin goals for common build operations for quickStart, portlet deployment, etc.
+ </li>
+ <li>
+ Preparation for future migration to Maven 2 (M2). With M2, custom goals are encapsulated in plugins, maven.xml
+ is deprecated. By centralizing most of the Jetspeed 2 build goals to the Jetspeed 2 Maven plugin, migration to
+ M2 should be much easier.
+ </li>
+ </ul>
+ </section>
+ <section name="Portal Application creation and configuration Goals">
+ <subsection name="Creating a new Portal Application">
+ <table>
+ <tr>
+ <th>Goal</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><code>j2:portal.genapp</code></td>
+ <td>
+ Generates or updates a custom portal application. <!--Checkout the
+ <a href="getting-started.html#4__Creating_a_new_Portal_Application">Getting Started</a>
+ document for basic usage of this goal.-->
+ <br />
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:portal.genapp.minimal</code></td>
+ <td>
+ Works similar to <code>j2:portal.genapp</code>. However, it
+ will only copy the following directories/files from <code>WEB-INF/pages</code>.
+ <ul>
+ <li>/WEB-INF/pages/Administrative/** (all contents)</li>
+ <li>/WEB-INF/pages/page.security</li>
+ </ul>
+ </td>
+ </tr>
+ </table>
+ </subsection>
+ <subsection name="Configuring and updating a Portal Application">
+ <p>
+ The <code>j2:portal.genapp</code> goal above is actually no more than a wrapper around several (sub)goals
+ which can also be used individually to update and configure your portal application:
+ </p>
+ <table>
+ <tr>
+ <th>Goal</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><code>j2:portal.copy.webapp</code></td>
+ <td>
+ Copies the (static) Jetspeed 2 portal web resource from the plugin to the
+ <code>${org.apache.jetspeed.portal.webapp.dir}</code> folder.
+ <br />
+ <br />
+ Running this goal again will not clear out previous resources but <i>will</i> overwrite existing resources.
+ <br />
+ <br />
+ If you need to upgrade to a newer version of the Jetspeed 2 portal you should clear out these resources
+ yourself first. By default, the target folder is configured within the maven default target folder and
+ running the <code>clear</code> goal will do exactly that.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:portal.copy.webapp.minimal</code></td>
+ <td>
+ Similar to <code>j2:portal.copy.webapp</code> However, it
+ will only copy the following directories/files from <code>WEB-INF/pages</code>.
+ <ul>
+ <li>/WEB-INF/pages/Administrative/** (all contents)</li>
+ <li>/WEB-INF/pages/page.security</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:portal.conf.project</code></td>
+ <td>
+ Creates a new maven or updates an existing portal project configuration in the
+ <code>${org.apache.jetspeed.portal.home.dir}</code> folder.
+ <br />
+ It creates a hiearchy of 5 maven project files:
+ <ul>
+ <li><code>project-info.xml</code></li>
+ <li><code>core-build.xml extends project-info.xml</code></li>
+ <li><code>jetspeed-components.xml extends core-build.xml</code></li>
+ <li><code>full-portal.xml extends jetspeed-components.xml</code></li>
+ <li><code>project.xml extends full-portal.xml</code></li>
+ </ul>
+ Of the above files, the first and the last (project-info.xml and project.xml) may be modified to provide
+ additional project information and configuration and will not be updated by this goal again. Only the
+ other 3 files will be rewritten by this goal. If you need to upgrade to a newer version of the Jetspeed 2
+ portal your own customization will be preserved.
+ <br />
+ <br />
+ Additionally, you can add your own maven.xml and/or project.properties or build.properties to further
+ customize your portal. These also will be preserverd when you run this goal again.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:portal.conf.sql</code></td>
+ <td>
+ Generates the portal sql schema DDL for the configured database(s) under the
+ <code>${org.apache.jetspeed.portal.sql.dir}</code>, as well as copies over statically defined common and
+ selected database specific sql DML and DDL (possibly overriding generated DDL).
+ <br />
+ <br />
+ The content of the sql target folder is cleared out first when this goal is run.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:portal.conf.ojb</code></td>
+ <td>
+ Copies the OJB configuration, filtered for the currently selected production database to the
+ <code>${org.apache.jetspeed.portal.target.dir}</code> folder.
+ <br />
+ <br />
+ As default, the above target folder is configured under the default maven war target folder. The maven
+ <code>clear</code> goal will also remove this filtered OJB configuration.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:portal.conf.ldap</code></td>
+ <td>
+ Copies the LDAP configuration, to the
+ <code>${org.apache.jetspeed.portal.target.dir}</code> folder.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:portal.conf.jetspeed</code></td>
+ <td>
+ Copies the filtered <code>jetspeed.properties</code> portal configuration to the
+ <code>${org.apache.jetspeed.portal.target.dir}</code> folder.
+ <br />
+ <br />
+ As default, the above target folder is configured under the default maven war target folder. The maven
+ <code>clear</code> goal will also remove this filtered <code>jetspeed.properties</code> file.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:portal.conf.tomcat</code></td>
+ <td>
+ Copies a filtered Tomcat context descriptor, containing current database connection configuration to the
+ <code>${org.apache.jetspeed.portal.conf.dir}</code> folder.
+ <br />
+ <br />
+ Based on the <code>${org.apache.jetspeed.catalina.major.version}</code> setting, a Tomcat 5.0.x or 5.5.x
+ type template context descriptor will be used.
+ <br />
+ <br />
+ The filtered Tomcat context descriptor will be copied to the Tomcat server by the
+ <code>j2:portal.deploy</code> goal.
+ <br />
+ <br />
+ If you need to change the Tomcat major version and/or database connection configuration, you need to
+ run this goal again before (re)deploying your portal.
+ <br />
+ <br />
+ As default, the above target folder is configured under the default maven target folder. The maven
+ <code>clear</code> goal will remove this filtered context descriptor file.
+ </td>
+ </tr>
+ </table>
+ </subsection>
+ </section>
+ <section name="Portal Application Deployment Goals">
+ <subsection name="Quickstart deployment goals">
+ <p>
+ Several goals are available for quickly deploying the Portal Application together with a predefined set of
+ Portlet Applications and optionally with creating and seeding the portal database.
+ </p>
+ <table>
+ <tr>
+ <th>Goal</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><code>j2:doStart</code></td>
+ <td>
+ A generic goal for deploying the portal application and setting up the required dependencies for the
+ configured Tomcat Server (shared libraries, portal application context, etc.).
+ <br />
+ <br />
+ This goal requires the plugin property <code>deployType</code> to be set. The default value is
+ <code>"j2:fullDeploy"</code> (see below).
+ <br />
+ <br />
+ If plugin property <code>recreateDB</code> is set, goal <code>j2:db.recreate</code> is invoked.
+ <br />
+ All existing Jetspeed 2 standard and demo portlet applications are removed through goal
+ <code>j2:remove.wars</code>.
+ <br />
+ The shared dependecies are copied to the Tomcat Server with goal <code>j2:copy.shared.deps</code>.
+ <br />
+ And finally, the set <code>deployType</code> plugin property value is used to run a specific deploy goal.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:quickStart</code></td>
+ <td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:fullDeploy"</code> and
+ <code>recreateDB=true</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:nodbQuickStart</code></td>
+ <td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:nodbfullDeploy"</code> and
+ <code>recreateDB=false</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:basicStart</code></td>
+ <td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:basicDeploy"</code> and
+ <code>recreateDB=true</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:nodbBasicStart</code></td>
+ <td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:nodbBasicDeploy"</code> and
+ <code>recreateDB=false</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:minStart</code></td>
+ <td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:minDeploy"</code> and
+ <code>recreateDB=true</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:nodbMinStart</code></td>
+ <td>
+ Invokes <code>j2:doStart</code> with <code>deployType="j2:nodbMinDeploy"</code> and
+ <code>recreateDB=false</code>.
+ </td>
+ </tr>
+ </table>
+ </subsection>
+ <subsection name="Deployment supporting Goals">
+ <table>
+ <tr>
+ <th>Goal</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td>j2:remove.wars</td>
+ <td>
+ Removes the portal, all standard and demo portlet applications (see <code>j2:fullDeploy</code> below)
+ and their context descriptors (if any) from the Tomcat Server.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:catalina.base.shared</code></td>
+ <td>
+ Copies all base jars necessary for the common portlet container.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:catalina.shared</code></td>
+ <td>Copies all jars necessary for common container</td>
+ </tr>
+ <tr>
+ <td><code>j2:copy.shared.deps</code></td>
+ <td>
+ Wrapper goal invoking <code>j2:catalina.base.shared</code> and <code>j2:catalina.shared</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:portal.deploy</code></td>
+ <td>
+ Deploys the portal application only and its dependencies to the Tomcat Server, but no portlet applications.
+ <br />
+ <br />
+ First, it removes the current portal installation with goal <code>j2:remove.wars</code>.
+ <br/>
+ Then it copies and expands the build portal war from the local maven repository to the application server.
+ <br />
+ And it copies a Tomcat context descriptor for the portal (see also goal <code>j2:portal.conf.tomcat</code>).
+ <br />
+ Finally, it installs the shared dependencies with goal <code>j2:copy.shared.deps</code>.
+ </td>
+ </tr>
+ </table>
+ </subsection>
+ <subsection name="Standard and Demo Portlet Application deployment goals">
+ <table>
+ <tr>
+ <th>Goal</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><code>j2:deploy</code></td>
+ <td>
+ Generic goal to deploy a portlet application identified by property <code>${maven.war.final.name}</code>.
+ <br />
+ <br />
+ The portlet application is searched for in the Jetspeed2 group of the local maven repository. When
+ searching portlets in the repository, this goal searches for the portlet application given the Jetspeed 2
+ version number configured in the plugin. The name of the file searched in the repository following the
+ convention <code>${maven.war.final.name}-${jetspeed.version}.war</code> and is deployed as
+ <code>${maven.war.final.name}.war</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.layoutdeploy</code></td>
+ <td>Deploys Jetspeed local layout portlet application.</td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.admindeploy</code></td>
+ <td>Deploys Jetspeed Administration portlet application.</td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.tsdeploy</code></td>
+ <td>Deploys Pluto Test Suite portlet application.</td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.strutsdeploy</code></td>
+ <td>Deploys the struts mailreader demo portlet application.</td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.jpetstoredeploy</code></td>
+ <td>Deploys the iBatis JPetstore based demo portlet application.</td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.jsfdeploy</code></td>
+ <td>Deploys the JSF demo portlet application which uses Jetspeed generic JSF portlet bridge.</td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.jsfmyfacesdeploy</code></td>
+ <td>Deploys the JSF demo portlet application which uses MyFaces native JSF portlet bridge.</td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.phpdeploy</code></td>
+ <td>Deploys the Jetspeed PHP bridge demo portlet application.</td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.perldeploy</code></td>
+ <td>Deploys the Jetspeed Perl bridge demo portlet application.</td>
+ </tr>
+ <tr>
+ <td><code>j2:pam.rssdeploy</code></td>
+ <td>Deploys the RSS feed demo portlet application.</td>
+ </tr>
+ <tr>
+ <td><code>j2:nodbMinDeploy</code></td>
+ <td>
+ Deploys the portal using the <code>j2:portal.deploy</code> goal and only the layout and admin portlets
+ using <code>j2:pam.layoutdeploy</code> and <code>j2:pam.admindeploy</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:minDeploy</code></td>
+ <td>
+ The same functionality as <code>j2:nodbMinDeploy</code> and additionaly seeds the portal database using
+ the <code>j2:db.entities</code> goal.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:nodbfullDeploy</code></td>
+ <td>
+ The same functionality as <code>j2:nodbMinDeploy</code> but additional deploys all other demo portlet
+ applications (see full list above).
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:fullDeploy</code></td>
+ <td>
+ The same functionality as <code>j2:nodbFullDeploy</code> and additionaly seeds the portal database using
+ the <code>j2:db.entities</code> goal.
+ </td>
+ </tr>
+ </table>
+ </subsection>
+ </section>
+ <section name="Database Management Goals">
+ <table>
+ <tr>
+ <th>Goal</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><code>j2:start.production.server</code></td>
+ <td>Starts a HSQLDB production database for usage by the portal. This goal is optional to those who use the default embedded Derby database.</td>
+ </tr>
+ <tr>
+ <td><code>j2:start.test.server</code></td>
+ <td>
+ Starts a HSQLDB test database to be used for the testcases during the build of Jetspeed 2.
+ This goal is optional for those who use the default embedded Derby database for testing Jetspeed 2.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:db.create.test</code></td>
+ <td>
+ Creates the test database tables. If using the HSQLDB database, it should be started first with
+ goal <code>j2:start.test.server</code>.
+ <br />
+ Existing portal tables are dropped first. The first time, this will lead to "table does not exist"
+ error messages but they can be (and are) ignored.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:db.create.production</code></td>
+ <td>
+ Creates the production database tables. If using the HSQLDB database, it should be started first
+ with goal <code>j2:start.production.server</code>.
+ <br />
+ Existing portal tables are dropped first. The first time, this will lead to "table does not exist"
+ kind of error messages but they can (and are) ignored.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:db.recreate</code></td>
+ <td>
+ Recreates the production database using the <code>j2:db.create.production</code> goal but first
+ (re)generates the sql scripts using <code>j2:portal.conf.sql</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:db.drop.test</code></td>
+ <td>Drops the test database portal tables.</td>
+ </tr>
+ <tr>
+ <td><code>j2:db.drop.production</code></td>
+ <td>Drops the production database portal tables.</td>
+ </tr>
+ <tr>
+ <td><code>j2:db.entities</code></td>
+ <td>
+ Populates the users information for the default PSML configuration configured with Jetspeed 2.
+ </td>
+ </tr>
+ </table>
+ </section>
+ <section name="LDAP Management Goals">
+ <table>
+ <tr>
+ <th>Goal</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><code>j2:start.ldap.server</code></td>
+ <td>Starts the default Apache Directory Server and load the default
+ <i><a href="http://svn.apache.org/viewcvs.cgi/portals/jetspeed-2/trunk/etc/apacheds/apacheds-server.xml?view=markup">apacheds-server.xml</a></i> configuration.</td>
+ </tr>
+ </table>
+ </section>
+ <section name="Auxillary Jetspeed Components Deployment Goals">
+ <p>
+ Generic set of goals for redeploying a specific Jetspeed component.
+ </p>
+ <table>
+ <tr>
+ <th>Goal</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><code>j2:jar.deploy</code></td>
+ <td>
+ Deploys a Jetspeed core component from the local maven repository to the deployment directory.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:jar.deploy.shared</code></td>
+ <td>
+ Deploys a Jetspeed core component shared library from the local maven repository to the Tomcat shared
+ library directory.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:deployDecorations</code></td>
+ <td>
+ Deploys all decoration files from the WEB-INF/decorations directory to the deployed portal.
+ </td>
+ </tr>
+ <tr>
+ <td><code>j2:deployTemplates</code></td>
+ <td>
+ Deploys all template files from the WEB-INF/templates directory to the deployed portal.
+ </td>
+ </tr>
+ </table>
+ </section>
+ </body>
+</document>
+
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/j2-maven-plugin.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/j2-maven-plugin.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/jetspeed-eclipse.xml
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/jetspeed-eclipse.xml?rev=768636&view=auto
==============================================================================
--- portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/jetspeed-eclipse.xml (added)
+++ portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/jetspeed-eclipse.xml Sun Apr 26 03:36:40 2009
@@ -0,0 +1,90 @@
+<?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>
+ Developing Jetspeed with Eclipse
+ </title>
+ <subtitle>How-to for Building and Debugging Jetspeed with Eclipse</subtitle>
+ <authors>
+ <person name="David Sean Taylor" email="taylor@apache.org" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Developing with Eclipse">
+ <subsection name="The Eclipse Classpath">
+ <p>
+ Compiling, debugging, external dependencies, source code completion, searching, auto imports, all rely on a properly configured classpath.
+ When you first create a project, a .classpath file is created in the projects root directory.
+ With the Jetspeed source, we provide you with a ready-to-use Eclipse .classpath file.
+ We have already configured the relative source directories for you.
+ Eclipse provides a .classpath GUI editor from the Project->Properties menu option.
+ </p>
+ </subsection>
+ <subsection name="JAR files and the Maven-1 repository">
+ <p>
+ Jetspeed requires quite a few JAR files to be able to compile.
+ The .classpath file that comes with Jetspeed is setup to get its JAR files out of a local Maven-1 repository.
+ You can see all the JAR file dependencies from Eclipse. Go to Project->Properties->Java Build Path->Libraries.
+ Notice all the JAR files are configured as VARIABLE library entries.
+ Take one example:
+ <source>
+ MAVEN_REPO/commons-lang/jars/commons-lang-2.0.jar
+ </source>
+ The Variable is portion is MAVEN_REPO.
+ The Extension portion is /commons-lang/jars/commons-lang-2.0.jar
+ Eclipse locates the JAR dependency from a Variable location root.
+ In order for this classpath to work correctly, the variable root is dependent on a Maven-1 local repository file structure.
+ </p>
+ <p>
+ To configure the MAVEN_REPO variable, go to Window->Preferences->Java->Build Path->Classpath Variables,
+ click on New, and define a new variable named MAVEN_REPO, pointing it out the root of your local Maven-1 repository,
+ usually someplace like your $HOME/.maven/repository.
+ </p>
+ </subsection>
+ <subsection name="JAR files and the Maven-2 repository">
+ <p>The same procedure applies for working a local Maven-2 repository.
+ We provide an alternative .classpath file found in the source code under <b>etc/editors/m2.classpath</b>.
+ Copy m2.classpath over the .classpath file in the project root.
+ </p>
+ <p>This classpath requires a different Eclipse classpath variable: M2_REPO.
+ To configure the M2_REPO variable, go to Window->Preferences->Java->Build Path->Classpath Variables,
+ click on New, and define a new variable named MAVEN_REPO, pointing it out the root of your local Maven-2 repository,
+ usually someplace like your $HOME/.m2/repository.
+ </p>
+ </subsection>
+ </section>
+ <section name="Debugging with Eclipse and Tomcat">
+ <p>Remote debugging of the Jetspeed Portal running on Tomcat requires that you start Tomcat up with debugging enabled.
+ Here is a shell script that can be used to debug:
+ </p>
+<source><![CDATA[
+export JPDA_TRANSPORT=dt_socket
+export JPDA_ADDRESS=8000
+./catalina.sh jpda start
+]]></source>
+<source><![CDATA[
+<p>A DOS script:</p>
+set JPDA_TRANSPORT=dt_socket
+set JPDA_ADDRESS=8000
+catalina jpda start
+]]></source>
+<p>From there, just follow the Eclipse documentation on how to remotely debug.</p>
+ </section>
+ </body>
+</document>
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/jetspeed-eclipse.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/jetspeed-eclipse.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/login-module.xml
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/login-module.xml?rev=768636&view=auto
==============================================================================
--- portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/login-module.xml (added)
+++ portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/login-module.xml Sun Apr 26 03:36:40 2009
@@ -0,0 +1,155 @@
+<?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 Security - Login Module</title>
+ <authors>
+ <person name="David Le Strat" email="dlestrat@apache.org" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Login Module Overview">
+ <p>
+ For authentication purpose, Jetspeed 2 provide a default login module implementation. Login modules provide a standard way to expose
+ authentication services for java application. More information about login modules can be found in the JDK
+ <a href="http://java.sun.com/j2se/1.4.2/docs/api/javax/security/auth/spi/LoginModule.html">LoginModule interface</a>
+ documentation.
+ </p>
+ </section>
+ <section name="Login Module Configuration">
+ <p>
+ Configuration is central to JAAS authentication. By default, Jetspeed 2 is configured to use its
+ <code>DefaultLoginModule</code>
+ implementation. The configuration file (login.conf) for the login module ship with the
+ <code>jetspeed2-security-{version}.jar</code>
+ component and provide the following configuration:
+ <source>
+ <![CDATA[
+Jetspeed {
+ org.apache.jetspeed.security.impl.DefaultLoginModule required;
+};]]>
+ </source>
+ </p>
+ <p>
+ In order to override this configuration, you can place your own login.conf file in your web application class path under WEB-INF/classes. The
+ location of the login.conf file is configured in the
+ <code>security-providers.xml</code>
+ as described below. For more information on how to configure the security providers, see
+ <a href="../deployguide/security-config.html">the configuration section</a>.
+ </p>
+ <p>
+ <source>
+ <![CDATA[
+<!-- Security: Default Authentication Provider -->
+<bean id="org.apache.jetspeed.security.AuthenticationProvider"
+ class="org.apache.jetspeed.security.impl.AuthenticationProviderImpl"
+>
+ <constructor-arg index="0"><value>DefaultAuthenticator</value></constructor-arg>
+ <constructor-arg index="1"><value>The default authenticator</value></constructor-arg>
+ <constructor-arg index="2"><value>login.conf</value></constructor-arg>
+ <constructor-arg index="3">
+ <ref bean="org.apache.jetspeed.security.spi.CredentialHandler"/>
+ </constructor-arg>
+ <constructor-arg index="4">
+ <ref bean="org.apache.jetspeed.security.spi.UserSecurityHandler"/>
+ </constructor-arg>
+</bean>]]>
+ </source>
+ </p>
+ <p>
+ The <code>AuthenticationProvider</code> configures the <code>LoginModule</code> to be used by the
+ application by setting the System property <code>java.security.auth.login.config</code> to the
+ <code>login.conf</code> specified in the component configuration.
+ </p>
+ </section>
+ <section name="Login Module Implementation">
+ <p>
+ The
+ <code>DefaultLoginModule</code>
+ implementation is illustrated by the class diagram below:
+ <br />
+ </p>
+ <table>
+ <tr>
+ <td style="background-color:#FFFFFF;" align="center">
+ <img src="images/default-login-module-c.gif" border="0" />
+ </td>
+ </tr>
+ </table>
+ <p>
+ The roles of the classes used to implement the DefaultLoginModule are:
+ </p>
+ <table>
+ <tr>
+ <th>Class</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><code>org.apache.jetspeed.security.impl.DefaultLoginModule</code></td>
+ <td>
+ The
+ <code>javax.security.auth.spi.LoginModule</code>
+ implementation. The
+ <code>DefaultLoginModule</code>
+ authentication decision is encapsulated behind the
+ <code>UserManager</code>
+ interface which leverages the SPI implementation to decide which authenticator should be used in order to authenticate a user against a
+ specific system of record. For more information on how to implement your own authenticator, see the
+ <a href="atn-spi.html">authentication SPI documentation</a>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>org.apache.jetspeed.security.LoginModuleProxy</code></td>
+ <td>
+ A utility component used to expose the
+ <code>UserManager</code>
+ to the
+ <code>DefaultLoginModule</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><code>org.apache.jetspeed.security.User</code></td>
+ <td>
+ The
+ <code>User</code>
+ is an interface that holds the
+ <code>javax.security.auth.Subject</code>
+ and his/her
+ <code>java.util.prefs.Preferences</code>. The
+ <code>UserManager</code>
+ upon user authentication populates the user subject with all user
+ <code>java.security.Principal</code>. Jetspeed 2 implements 3 types of principals:
+ <ul>
+ <li>UserPrincipal: The principal holding the user unique identifier for the application.</li>
+ <li>RolePrincipal: The principal representing a role for the system.</li>
+ <li>GroupPrincipal: The principal representing a group for the system.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><code>org.apache.jetspeed.security.UserManager</code></td>
+ <td>
+ The interface exposing all user operations. This interfaces fronts the aggregates various SPI to provide developers with the ability to
+ map users to their specific system of record.
+ </td>
+ </tr>
+ </table>
+ </section>
+
+ </body>
+</document>
\ No newline at end of file
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/login-module.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/login-module.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/new-security.xml
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/new-security.xml?rev=768636&view=auto
==============================================================================
--- portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/new-security.xml (added)
+++ portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/new-security.xml Sun Apr 26 03:36:40 2009
@@ -0,0 +1,160 @@
+<?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>Security 2.2</title>
+ <subtitle>New Security in Version 2.2</subtitle>
+ <authors>
+ <person name="Dennis Dam" email="ddam@apache.org" />
+ <person name="David Sean Taylor" email="taylor@apache.org" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Jetspeed Security Framework">
+ <p>With version 2.2, Jetspeed introduces a new security framework. The 2.2 security is based on an security association engine, enable you to introduce your own
+ security components and build associations with other existing or new security components.</p>
+ <subsection name="Key Concepts: Subjects, Principals, Credentials">
+ <p>
+Jetspeed supports Subject-based security as defined by JAAS (Java Authentication and Authorization Services).
+A subject is an aggregation of security information for a security entity, like a person.
+A subject can have several identities, also called principals. For example, a user logging into a
+Jetspeed portal is associated with one Subject, which contains a user principal, zero or more role principals, zero or more group principals, etc.
+Each principal can be associated with a set of permissions that allow the user to perform certain actions, like accessing a page, updating secured objects, etc.
+Finally, user principals in Jetspeed can be associated with a credential. A credential is, simply put, a username / password combination.
+ </p>
+ </subsection>
+ <subsection name="Jetspeed Security Component">
+ <p>
+All the security identity information above is managed by the Jetspeed Security Component. The Jetspeed Security Component provides a mechanism to access and update principal,
+ credential and permission data. When a user is authenticated in Jetspeed, a user principal is resolved for that user, based on the credentials that the user provided on login.
+ A user principal can then be associated with several other principals, which can be of the same (user principal) or different type (e.g. role, group, ..).
+ Principals are resolved in a nested manner, which means that each principal that is associated with the user principal can also be associated with other principals,
+ which can in turn be associated with other principals, etc. The final collection of principals found in this way is aggregated and attached to the Subject that is
+ resolved for the authenticated user. The Subject is used throughout Jetspeed for security purposes and can also be used by portlet applications to secure custom objects
+ using standard JAAS API.
+ </p>
+ </subsection>
+ <subsection name="Pluggable Security Architecture: Adapting to Different Security Models">
+ <p>
+Every project usually requires different security models, with meaningful relations between security principals that make sense for that project.
+Most projects can get away with using standard principal types like users, roles and groups, with regular associations between those principal types,
+like a user being a member of a role or group, a group being a member of a role, etc. There are also projects however, which go beyond that and require
+new principal types and custom associations between principal types. These projects create the need for a pluggable security architecture where new principal types
+ and principal associations can be added easily. This is exactly what the Jetspeed Security Component provides. This is best explained by illustrating
+ a custom security model, where a user is related to an organization. Jetspeed contains built-in support for users, groups and roles and associations between those,
+ but not for organizations and associations between users and organizations. To achieve that though, the following changes can be made to plugin organizations:
+ </p>
+<ul>
+<li>create a new class "Organization", implementing JetspeedPrincipal</li>
+<li>implement an OrganizationManager, based on the BaseJetspeedPrincipalManager.</li>
+<li>configure an "isMemberOf" association handler between a user and organization principal type</li>
+</ul>
+ <p>
+The OrganizationManager is a strongly typed manager with methods for accessing and storing organizations. The BaseJetspeedPrincipalManager class however, is a weakly typed manager,
+ which only operates on abstract principals. This means that for the most part, the OrganizationManager class can delegate back to the base class, except for some specific
+ organization handling and typecasting abstract principals back to organization instances.
+ </p>
+ <p>
+Configuring an association between users and organizations is in this case very simple, because an "isMemberOf" association handler is provided by default by Jetspeed.
+Configuring it is a matter of specifying a new instance of that handler and wiring it to both the UserManager and the OrganizationManager.
+ The custom security model setup is depicted in Figure 1.
+ <img src="images/extending-organization.jpg"/>
+ <i>Figure 1: Extending the security model with organizations</i>
+ </p>
+ </subsection>
+ <subsection name="Principals and Attributes">
+ <p>
+A Jetspeed principal is basically nothing more than a set of security attributes describing the principal.
+The attributes are custom and can differ per project. A user principal for example, can have contact information attributes.
+ An organization principal (from the example above) can have geographical coordinates of the office as an attribute.
+ The set of allowed attributes can be configured through Spring for each principal type.
+ Besides the attributes, a principal also has several constraints in its usage and access that can be configured,
+ such as whether the principal is read-only, can be removed, is enabled, etc.
+ </p>
+ </subsection>
+ <subsection name="Principal Associations">
+ <p>
+A principal association is a relation between two principals, where the relation always has a direction: it goes from one principal to another. For example,
+ in the relation "user is part of a group", the user is the starting point of the relation (the from principal) and the group is the ending point of the relation (the to principal).
+ The naming convention using "to" and "from" is used in the Jetspeed Security API. An example is a method in the JetspeedPrincipalManager interface called getAssociatedTo(..),
+ which fetches a list of associated principals given the name of a principal representing the "to" side of the association, and given the type of association.
+ The list of principals returned represent the "from" principals in the association. Associations have several characteristics, that influence the creation and deletion of
+ the principals in the association, or affect the way associations can be made between principals. The following list contains an overview of these characteristics:
+ </p>
+ <table>
+ <tr>
+ <th>Characteristic</th>
+ <th> Description</th>
+ </tr>
+ <tr>
+ <td>required</td>
+ <td>the "from" principal cannot be created without this association</td>
+ </tr>
+ <tr>
+ <td>dependent</td>
+ <td>the "from" principal will be deleted when the "to" principal is deleted</td>
+ </tr>
+ <tr>
+ <td>singular</td>
+ <td>the "from" principal can be associated from at most once</td>
+ </tr>
+ <tr>
+ <td>dominant</td>
+ <td>the "to" principal can be associated to at most once</td>
+ </tr>
+ </table>
+ <p>
+ All these characteristics are configured for an association through Spring.
+ </p>
+ <p>
+The built-in implementations of associations by Jetspeed are (and should be) independent of specific principal types. The advantage of that is that associations
+are pluggable and can be re-used between different pairs of principal types.
+ </p>
+ </subsection>
+ <subsection name="Storage of Principals and Associations">
+ <p>
+The storage engine of the Jetspeed Security Component uses a database to store and retrieve security data. By only allowing one type of data store,
+the storage and retrieval methods used internally by Jetspeed can be optimized and fine-tuned. An additional advantage is that more complex queries
+ on security data are possible, which would be difficult to achieve if the storage engine was abstracted in such a way that any data store could be supported.
+ </p>
+ <p>
+If the security model in Jetspeed is extended with new principals and/or associations, nothing has to be changed in database scripts or other code related to database.
+Jetspeed's generic storage engine will take care of storing and retrieving data.
+Although the storage engine works on top of a database internally, you have the possibility to synchronize data from another datastore. This will be discussed in the next section.
+ </p>
+ </subsection>
+ <subsection name="Synchronization and Replication">
+ <p>
+Security data can be synchronized from an external data store, and mapped to the database used internally by Jetspeed. Currently, LDAP is the only type of external
+data store supported by Jetspeed. LDAP data can be synchronized periodically, on startup or on authentication of a user. When synchronizing on authentication of a user,
+only the data related to that user is synchronized. Replication refers to writing back security data to the external store whenever security data in the database is updated.
+Synchronization is a mechanism which ensures that the contents of the external data store are the same as the internal database, where the external datastore has the highest
+priority. LDAP synchronization and replication is discussed in more detail in the LDAP Mapping guide.
+ </p>
+ </subsection>
+ <subsection name="Credentials">
+ <p>
+ </p>
+ </subsection>
+ <subsection name="Permissions">
+ <p>
+ </p>
+ </subsection>
+ </section>
+ </body>
+</document>
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/new-security.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/new-security.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/patches.xml
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/patches.xml?rev=768636&view=auto
==============================================================================
--- portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/patches.xml (added)
+++ portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/patches.xml Sun Apr 26 03:36:40 2009
@@ -0,0 +1,44 @@
+<?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 Jetspeed-2 Development</title>
+ <subtitle>Guide to Jetspeed-2 Development</subtitle>
+ <authors>
+ <person name="David Le Strat" email="dlestrat@apache.org" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Guide to Jetspeed-2 Development">
+ <subsection name="Working with Jetspeed-2 Source Code">
+ <p>
+ For information on how to get started with Jetspeed-2 source code, check
+ <a href="maven-2-build.html">Building Jetspeed 2.1.x from Source with Maven-2</a>.
+ </p>
+ </subsection>
+ <subsection name="How to Submit Patches?">
+ <p>
+ 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" />
+ </p>
+ </subsection>
+ </section>
+ </body>
+</document>
\ No newline at end of file
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/patches.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/patches.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/permission.xml
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/permission.xml?rev=768636&view=auto
==============================================================================
--- portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/permission.xml (added)
+++ portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/permission.xml Sun Apr 26 03:36:40 2009
@@ -0,0 +1,81 @@
+<?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 Security - PermissionManager Overview</title>
+ <authors>
+ <person name="David Le Strat" email="dlestrat@apache.org" />
+ </authors>
+ </properties>
+ <body>
+ <section name="PermissionManager Overview">
+ <p>The <code>PermissionManager</code> is used by the <code>RdbmsPolicy</code> to get the permissions for
+ a given user principals as presented
+ in the <a href="atz-jaas.html#Jetspeed_JAAS_Policy">Jetspeed JAAS Policy</a> section of the documentation.
+ </p>
+ <p>
+ The <code>PermissionManager</code> manages the association between permissions and principals. Each permission
+ or principal maps to a generic object model and reflexion is used to instantiate the proper permission or
+ principal type. The class diagram below represents the interfaces representing a generic permission
+ (<code>InternalPermission</code>) and a generic principal (<code>InternalPrincipal</code>) and their relation
+ to the <code>PermissionManager</code>.
+ </p>
+ <p>
+ <img src="images/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" />
+ </p>
+ </section>
+ <section name="Schema and OJB Mapping">
+ <p>
+ The OJB mappings for the security component are described in <code>security_repository.xml</code>:
+ <ul>
+ <li><code>InternalPrincipal</code>: Maps to the <code>SECURITY_PRINCIPAL</code> table.</li>
+ <li><code>InternalPermission</code>: Maps to the <code>SECURITY_PERMISSION</code> table.</li>
+ <li>Associations between <code>InternalPrincipal</code> and <code>InternalPermission</code> are
+ maintained through the indirection table <code>PRINCIPAL_PERMISSION</code>.</li>
+ </ul>
+ <source><![CDATA[
+<class-descriptor
+ class="org.apache.jetspeed.security.om.impl.InternalPrincipalImpl"
+ proxy="dynamic"
+ table="SECURITY_PRINCIPAL"
+ >...</class-descriptor>
+
+<class-descriptor
+ class="org.apache.jetspeed.security.om.impl.InternalPermissionImpl"
+ proxy="dynamic"
+ table="SECURITY_PERMISSION"
+ >...</class-descriptor>
+ ]]>
+ </source>
+ </p>
+ <p>
+ The relational schema maintaining principal to permission associations is provided below:
+ </p>
+ <p>
+ <img src="images/permissions-principals-schema.gif" border="0" />
+ </p>
+ </section>
+ </body>
+</document>
\ No newline at end of file
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/permission.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/permission.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/spring-config.xml
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/spring-config.xml?rev=768636&view=auto
==============================================================================
--- portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/spring-config.xml (added)
+++ portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/spring-config.xml Sun Apr 26 03:36:40 2009
@@ -0,0 +1,177 @@
+<?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>
+ Conditional Configuration Jetspeed 2.2 Components
+ </title>
+ <subtitle>How-to configure Jetspeed 2.2 Portal</subtitle>
+ <authors>
+ <person name="Ate Douma" email="ate@apache.org" />
+ <person name="Woonsan Ko" email="woonsan@apache.org" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Configuring Jetspeed Components">
+ <p>Jetspeed provides very flexible ways for specific configuration settings.</p>
+ <p>Jetspeed components are initially loaded from <strong><code>/WEB-INF/assembly/</code></strong> folder, while the default configuration properties are loaded from <strong><code>/WEB-INF/conf/jetspeed.properties.</code></strong></p>
+ <p>The initial/default configurations can be overrided through the <strong><code>/WEB-INF/assembly/override/</code></strong> folder, while overrides/additional values can be provided through the <strong><code>/WEB-INF/conf/override.properties.</code></strong></p>
+ <p>Another new feature is conditional Spring assembly loading. Jetspeed provides an extended BeanFactory
+ which checks a loaded Spring BeanDefinition for some extra meta data (defined within the Spring configuration itself)
+ against a predefined configuration, registering a BeanDefinition within Spring can be "prevented", effectively
+ filtering out certain definitions.</p>
+ </section>
+ <section name="Conditional Spring Assembly Loading">
+ <subsection name="Jetspeed Category Meta Data">
+ <p>
+ In Jetspeed assembly files, a bean definition should have <strong><code>j2:cat</code></strong> meta data like the following example:
+ <div class="source"><pre><bean name="xmlPageManager" class="org.apache.jetspeed.page.psml.CastorXmlPageManager">
+ <meta key="j2:cat" value="xmlPageManager or pageSerializer" />
+ ...
+</bean></pre></div>
+ In the above example, the <strong><code>xmlPageManager</code></strong> bean definition is included for two categories: <strong><code>xmlPageManager</code></strong> and <strong><code>pageSerializer</code></strong>.
+ If the Spring filter key setting of Jetspeed contains one of the categories, then the <strong><code>xmlPageManager</code></strong> bean definition will be registered. Otherwise, the bean definition will be ignored. By the Spring filter key setting, bean definitions in assembly files will be filtered according to their categories.
+ </p>
+ </subsection>
+ <subsection name="Spring Filter Keys and Categories Settings">
+ <p>The Spring filter settings of Jetspeed are defined in <strong><code>/WEB-INF/conf/spring-filter.properties</code></strong>.</p>
+ <p>In the file, the following category definitions are provided by default:
+ <table>
+ <tr>
+ <th>Filter Key</th>
+ <th>Mapped Categories</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td>default</td>
+ <td>default</td>
+ <td>Default category for most common components</td>
+ </tr>
+ <tr>
+ <td>basePortal</td>
+ <td>${default}, jndiDS, xmlPageManager</td>
+ <td>
+ The base category for a portal instance, to be used for other cateogry definitions.
+ In this category, the data source component and xml-based page manager are provided.
+ </td>
+ </tr>
+ <tr>
+ <td>portal</td>
+ <td>${basePortal}, dbSecurity</td>
+ <td>
+ The default category for a portal instance.
+ With the components by the basePortal category, the security components based on database are provided.
+ </td>
+ </tr>
+ <tr>
+ <td>portal.ldap</td>
+ <td>${basePortal}, ldapSecurity</td>
+ <td>
+ A category for a portal instance.
+ With the components by the basePortal category, the security components based on LDAP are provided.
+ </td>
+ </tr>
+ <tr>
+ <td>portal.dbPageManager</td>
+ <td>${default}, jndiDS, dbPageManager, dbSecurity</td>
+ <td>
+ A category for a portal instance.
+ In this category, the default components, the data source component and database-based page manager and database-based security components are provided.
+ </td>
+ </tr>
+ <tr>
+ <td>portal.dbPageManager.ldap</td>
+ <td>${default}, jndiDS, dbPageManager, ldapSecurity</td>
+ <td>
+ A category for a portal instance.
+ In this category, the default components, the data source component and database-based page manager and LDAP-based security components are provided.
+ </td>
+ </tr>
+ <tr>
+ <td>baseSerializer</td>
+ <td>jdbcDS, serializer, capabilities, security, profiler, registry, search, transaction, cache, prefs, springProperties, noRequestContext, noPageManager</td>
+ <td>
+ The base category for Jetspeed Serializer, to be used for other serializer cateogry definitions.
+ In this category, the necessary components for seeding and serializing Jetspeed data are provided.
+ </td>
+ </tr>
+ <tr>
+ <td>serializer</td>
+ <td>${baseSerializer}, dbSecurity</td>
+ <td>
+ The default category for serializer. In this category, database-based security components are provided.
+ </td>
+ </tr>
+ <tr>
+ <td>serializer.ldap</td>
+ <td>${baseSerializer}, ldapSecurity</td>
+ <td>
+ A category for serializer. In this category, LDAP-based security components are provided.
+ </td>
+ </tr>
+ <tr>
+ <td>pageSerializer</td>
+ <td>jdbcDS, base, pageSerializer, transaction, springProperties, security, dbSecurity, cache</td>
+ <td>
+ A category for page serializer.
+ </td>
+ </tr>
+ </table>
+ </p>
+ <p><em>Note: the expression enclosed by ${} will be expanded by the referenced property values.</em></p>
+ <p>
+ By default, the filter key of a portal instance is set to <strong><code>portal</code></strong>. To change this, you may define a property, <strong><code>spring.filter.key</code></strong> in one of the following properties files:
+ <strong><code>/WEB-INF/conf/spring-filter-key.properties</code></strong>, <strong><code>/WEB-INF/conf/override.properties</code></strong> or <strong><code>/WEB-INF/conf/jetspeed.properties</code></strong>.
+ For example, you can use Jetspeed Portal with LDAP-based Security components:
+ <div class="source"><pre>spring.filter.key = portal.ldap</pre></div>
+ </p>
+ </subsection>
+ <subsection name="Spring Filter Keys and Dynamic Bean Aliasing">
+ <p>Because the ids of every beans must be unique within the BeanFactory or ApplicationContext the bean is hosted in, we cannot use same bean id for several different beans.</p>
+ <p>For example, there could be two options to choose page manager bean component: xml-based page manager or database-based page manager. If some other beans should refer the filtered page manager, they should be grouped in a same category as the filtered page manager. So, there should be many redundant bean definitions which make the maintenance very difficult.</p>
+ <p>Therefore, Jetspeed provides a way to alias beans dynamically with spring bean filtering solution.
+ In the following example, the first two bean definitions do not have id, but they have the same <strong><code>j2:alias</code></strong> meta data value. Jetspeed custom BeanFactory register the alias(es) dynamically according to this meta data.
+ Finally, the last bean definition can refer the selected bean by using the alias, <strong><code>org.apache.jetspeed.page.PageManager</code></strong>.
+ <div class="source"><pre><bean class="org.springframework.beans.factory.config.BeanReferenceFactoryBean">
+ <meta key="j2:cat" value="xmlPageManager" />
+ <meta key="j2:alias" value="org.apache.jetspeed.page.PageManager" />
+ <property name="targetBeanName" value="xmlPageManager" />
+</bean>
+
+<bean class="org.springframework.beans.factory.config.BeanReferenceFactoryBean">
+ <meta key="j2:cat" value="dbPageManager" />
+ <meta key="j2:alias" value="org.apache.jetspeed.page.PageManager" />
+ <property name="targetBeanName" value="dbPageManager" />
+</bean>
+
+<bean id="org.apache.jetspeed.portalsite.PortalSite" name="portalSite"
+ class="org.apache.jetspeed.portalsite.impl.PortalSiteImpl">
+ <meta key="j2:cat" value="default" />
+ <constructor-arg index="0">
+ <ref bean="org.apache.jetspeed.page.PageManager" />
+ </constructor-arg>
+</bean></pre>
+ </div>
+ </p>
+ <p>
+ <em>Note: multiple alias names can be set to j2:alias meta data value by a string separated by comma or space.</em>
+ </p>
+ </subsection>
+ </section>
+ </body>
+</document>
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/spring-config.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-dev/src/site/xdoc/spring-config.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/pom.xml
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/pom.xml?rev=768636&view=auto
==============================================================================
--- portals/site/jetspeed-2.2/jetspeed-guide-users/pom.xml (added)
+++ portals/site/jetspeed-2.2/jetspeed-guide-users/pom.xml Sun Apr 26 03:36:40 2009
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
+ $Id$
+-->
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
+
+ <modelVersion>4.0.0</modelVersion>
+ <prerequisites>
+ <maven>2.0.9</maven>
+ </prerequisites>
+
+ <artifactId>jetspeed-guide-users</artifactId>
+ <name>Jetspeed Users Guide</name>
+ <description>Jetspeed Users Guide</description>
+ <!-- FIXME: this causes an NPE in maven dearest
+ <parent>
+ <groupId>org.apache.portals.jetspeed-2</groupId>
+ <artifactId>jetspeed-docs</artifactId>
+ <version>2.2</version>
+ </parent>
+ <packaging>pom</packaging>
+ -->
+ <groupId>org.apache.portals.jetspeed-2</groupId>
+ <version>2.2</version>
+
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-project-info-reports-plugin</artifactId>
+ <reportSets>
+ <reportSet>
+ <reports>
+ </reports>
+ </reportSet>
+ </reportSets>
+ </plugin>
+ </plugins>
+ </reporting>
+
+</project>
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/pom.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/pom.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/2column.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/2column.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/2column.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/4column.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/4column.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/4column.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/addportlet.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/addportlet.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/addportlet.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/arrowsxbar.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/arrowsxbar.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/arrowsxbar.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/breadcrumbs.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/breadcrumbs.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/breadcrumbs.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/categories.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/categories.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/categories.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/customfolder.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/customfolder.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/customfolder.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/customize.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/customize.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/customize.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/customtab.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/customtab.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/customtab.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/decoratordiagram.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/decoratordiagram.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/decoratordiagram.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/deskcustom.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/deskcustom.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/deskcustom.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/deskplus.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/deskplus.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/deskplus.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/desktop.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/desktop.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/desktop.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/dropdowncolumns.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/dropdowncolumns.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/dropdowncolumns.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/dropdownlayout.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/dropdownlayout.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/dropdownlayout.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/dropdowntheme.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/dropdowntheme.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/dropdowntheme.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/editactionbar.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/editactionbar.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/editactionbar.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/editicon.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/editicon.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/editicon.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/folderconfig.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/folderconfig.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/folderconfig.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/forgotten.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/forgotten.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/forgotten.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/helpicon.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/helpicon.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/helpicon.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/indportlettheme.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/indportlettheme.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/indportlettheme.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/infoicon.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/infoicon.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/infoicon.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/layconfig.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/layconfig.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/layconfig.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/leftmenu.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/leftmenu.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/leftmenu.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/leftmove.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/leftmove.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/leftmove.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/localedropdown.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/localedropdown.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/localedropdown.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/login.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/login.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/login.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/maxicon.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/maxicon.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.
Propchange: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/maxicon.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/minicon.png
URL: http://svn.apache.org/viewvc/portals/site/jetspeed-2.2/jetspeed-guide-users/src/site/resources/images/minicon.png?rev=768636&view=auto
==============================================================================
Binary file - no diff available.