Skip to content

Commit

Permalink
This commit was manufactured by cvs2svn to create tag 'rel-2-4-2'.
Browse files Browse the repository at this point in the history
git-svn-id: https://source.jasig.org/uPortal/tags/rel-2-4-2@9867 f5dbab47-78f9-eb45-b975-e544023573eb
  • Loading branch information
infrastructure@lists.ja-sig.org committed Jan 22, 2005
1 parent 880bb63 commit acf13ca
Show file tree
Hide file tree
Showing 163 changed files with 4,046 additions and 2,112 deletions.
30 changes: 30 additions & 0 deletions LICENSE.txt
@@ -0,0 +1,30 @@
Copyright 2000-2005 The JA-SIG Collaborative. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.

3. Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes software developed by the JA-SIG Collaborative
(http://www.jasig.org/)."

THIS SOFTWARE IS PROVIDED BY THE JA-SIG COLLABORATIVE "AS IS" AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JA-SIG COLLABORATIVE OR
ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.
111 changes: 111 additions & 0 deletions README.txt
@@ -0,0 +1,111 @@
$Id$

uPortal Distribution
--------------------------

Purpose
-------
This distribution is targeted towards
people who would like to install
uPortal in a development or production
environment. It contains uPortal source
code and properties files, but not a servlet
container, directory, or relational database,
which are required. Use of this distribution
requires knowledge of J2EE environments and the
Ant tool from the Apache Jakarta project.


Contents
--------
1) uPortal
2) uPortal dependencies (Xalan, Pluto, etc).
3) uPortal Architecture overview and JavaDoc API


System requirements
-------------------
JDK 1.4 or higher
JAVA_HOME environment variable must be set
Installation of Ant from Jakarta:
http://ant.apache.org/


Instructions
------------
Modify build.properties with local settings.

Use the following ant targets:

initportal - installs uPortal into a servlet container,
prepares a relational database with uPortal schema and data,
publishes channels and layout fragments,
deploys portlet applications
dist - creates JavaDoc, uPortal jar, and uPortal WAR files.

For descriptions of other Ant targets,
see docs/uPortal_tools_overview.txt.

Make sure the database and servlet container are running and
access uPortal with http://localhost:8080/uPortal/
Your URL may be different if you have configured a different port
and/or context name.

You can login to uPortal with the following user name/password
combinations:

demo, demo
student, student
faculty, faculty
staff, staff
developer, developer

Each user may have a slightly different layout.


Notes
-----
-Several properties files and one database table changed
since uPortal 2.3.x. If you are upgrading from this version,
you will need to see to it that your properties files and
database data are upgraded appropriately. The difficulty
of upgrading from 2.3.x to 2.4.x is expected to be much lower
than similar upgrades in past versions.

-uPortal does not strictly require the use of connection
pooling, but it is highly recommended for production
installations. If your servlet container does not provide
connection pooling, try something like Yet Another Poolman.
For information about Yet Another Poolman,
see http://yapoolman.sourceforge.net/.

-Bug fixes from 2.3.x releases have been implemented in 2.4.x
whenever they were appropriate

-If you experience XML/XSLT-related errors, there is a good
chance that your environment is not using the version of
Xalan/Xerces that comes with this release. If you are using
Tomcat, try copying the following files into Tomcat's
common/endorsed directory: xalan.jar, xercesImpl.jar, xml-apis.jar.
Alternatively, you can specify the use of these jar files
via a java parameter when starting your servlet container:
-Xbootclasspath/p:xalan.jar;xercesImpl.jar;xml-apis.jar
For more information, see Version section of
http://xml.apache.org/xalan-j/faq.html

-JSR 168 Portlets are supported in this version of uPortal.
For information on installing Portlets, see
http://www.uportal.org/implementors/portlets/workingWithPortlets.html.

-WSRP functionality was included in uPortal as early as uPortal 2.2.
However, beginning with uPortal 2.4, the WSRP consumer has been replaced with
one based on WSRP4J. The WSRP producer has been deprecated but may
be reintroduced in a future release.

Please report bugs and suggestions:

http://www.uportal.org/bugzilla/

uPortal website:

http://www.uportal.org
49 changes: 49 additions & 0 deletions RELEASE_NOTES.txt
@@ -0,0 +1,49 @@
$Id$

uPortal Release Notes
---------------------

Release Notes - uPortal - Version 2.4.2

** Bug
* [UP-338] - RENDERING_DONE Event never sent
* [UP-476] - User's LDAP groups not loaded if username contains uppercase
* [UP-512] - User agent too long for db column
* [UP-685] - wrong fname in fragment produces exception with no useful error
message
* [UP-744] - PersonDirectory has a memory leak related to caching IPersons in
a WeakHashMap
* [UP-745] - ChannelManager has a memory leak, when it swaps out a channel
for the CError channel, the end session events never progagate
to the original channel
* [UP-746] - CSecureInfo has a memory leak, when ChannelManager swaps out a
channel for the CSecureInfo channel, the to end session events
never propagate to the original channel
* [UP-747] - Change to portlet parameter encoding breaks download worker URLs
* [UP-748] - Infinite recursion in RestrictedPerson
* [UP-749] - render parameter does not survive refresh
* [UP-753] - ChannelFactory should not expose internal map of static channels,
not create more than one instance of a multithreaded channel
* [UP-758] - CContentSubscriber prints exception to stdout instead of log
* [UP-759] - Xalan jar should be deployed to endorsed directory
* [UP-760] - Entity locks not expired correctly
* [UP-761] - A lock owner is limited to single READ lock on an entity
* [UP-772] - Classpath resources not being copied to build
* [UP-775] - Duplicate read locks for a single owner not permitted.
* [UP-776] - WebApplicationMarshaller.java turns resource-ref into
resource-env-ref
* [UP-778] - AggregatedLayoutManager.loadUserLayout() fails to log stack
trace for exception
* [UP-779] - ChannelRenderer declares constants that are already declared
in its base class
* [UP-780] - Eliminate "unknown additional descriptor warning" when using
ChainingSecurityContext
* [UP-796] - contains() doesn't always work for PAGS groups
* [UP-798] - GroupService.isComposite always returns null
* [UP-811] - NPE when Data tag not present in DatabaseTagHandler

** Improvement
* [UP-770] - Document hsqldb version included with uPortal
* [UP-800] - Add comment to clarify usage of Logger.properties
* [UP-809] - Move portlet request attribute configuration to helper method
* [UP-810] - Log logging implementation
6 changes: 3 additions & 3 deletions build.properties
Expand Up @@ -15,10 +15,10 @@
#==================== File and Directory Names ========================

app.name=uPortal
app.version=2.4
app.version=2.4.2

lib.path=lib
server.home=/JavaClasses/jakarta-tomcat-5.0.25
server.home=/JavaClasses/jakarta-tomcat-5.0.28

deploy.home=${server.home}/webapps/uPortal

Expand Down Expand Up @@ -49,7 +49,7 @@ wsdl4j.jar=${lib.path}/wsdl4j.jar
commons-discovery.jar=${lib.path}/commons-discovery.jar
commons-logging.jar=${lib.path}/commons-logging.jar
portlet-api.jar=${lib.path}/portlet-api-1.0.jar
pluto.jar=${lib.path}/pluto-1.0.1.jar
pluto.jar=${lib.path}/pluto-1.0.1-rc1.jar
wsrp4j-shared.jar=${lib.path}/wsrp4j-shared-0.3.jar
wsrp4j-consumer.jar=${lib.path}/wsrp4j-consumer-0.3.jar
proxyportlet.jar=${lib.path}/proxyportlet.jar
Expand Down
54 changes: 19 additions & 35 deletions build.xml
Expand Up @@ -237,20 +237,20 @@
URL: http://jakarta.apache.org/commons/logging.html
portlet-api.jar Portlet API based on JSR-168.
Version: (from jakarta-pluto CVS on September 22, 2004)
Version: (from jakarta-pluto CVS on November 2, 2004)
URL: http://www.jcp.org/en/jsr/detail?id=168
pluto.jar Reference Implementation of the Java Portlet Specfication.
This Portlet container provides a runtime environment for
portlets implemented according to the Portlet API.
The project is still in the Apache Incubator.
Version: (from jakarta-pluto CVS on September 22, 2004)
Version: (from jakarta-pluto CVS on November 2, 2004)
URL: http://portals.apache.org/pluto/
wsrp4j-shared.jar WSRP4J shared classes mostly derived from OASIS WSRP WSDL.
Comes with WSRP4J.
Use the version that comes with WSRP4J.
Version: (from ws-wsrp4j CVS on July 9, 2004)
Version: (from ws-wsrp4j CVS on November 2, 2004)
URL: http://ws.apache.org/wsrp4j/
wsrp4j-consumer.jar WSRP4J consumer classes.
Expand All @@ -264,20 +264,6 @@
The following modifications were made to the
WSRP4J proxy portlet source:
- org.apache.wsrp4j.consumer.portlet.impl.ProxyPortlet:
IS: protected PortletKey getPortletKey(Map preferences)
WAS: private PortletKey getPortletKey(Map preferences)
IS: protected Producer getProducer(String producerID) throws WSRPException
WAS: private Producer getProducer(String producerID) throws WSRPException
Added new method
protected ConsumerEnvironment getConsumerEnvironment()
{
return consumerEnv;
}
- portlet.xml
Expand All @@ -286,7 +272,7 @@
IS: <value>org.jasig.portal.wsrp.consumer.portlet.ConsumerEnvironmentImpl</value>
WAS: <value>org.apache.wsrp4j.consumer.portlet.impl.ConsumerEnvironmentImpl</value>
- wsrp4j-logger.properties
IS: log4j.appender.A1.File=wsrp4j-consumer.log
Expand Down Expand Up @@ -469,6 +455,11 @@
<classpath refid="compile.classpath"/>
</javac>

<!-- Copy non-java resources -->
<copy todir="${build.home}/WEB-INF/classes">
<fileset dir="source" excludes="CVS,**/*.java"/>
</copy>

<!-- Copy associated resource files -->
<copy todir="${build.home}/WEB-INF/classes/properties">
<fileset dir="properties" includes="**/*"/>
Expand All @@ -477,11 +468,6 @@
<!-- Copy the Logger.properties file to the well-known location
log4j expects.-->
<copy file="properties/Logger.properties" tofile="${build.home}/WEB-INF/classes/log4j.properties"/>

<!-- Copy serializer resources -->
<copy todir="${build.home}/WEB-INF/classes/org/jasig/portal/serialize">
<fileset dir="source/org/jasig/portal/serialize" includes="**/*.res"/>
</copy>

<!-- Copy all stylesheets, stylesheet descriptions and stylesheet list files -->
<copy todir="${build.home}/WEB-INF/classes">
Expand Down Expand Up @@ -528,7 +514,6 @@

<!-- Copy external dependencies as required -->
<mkdir dir="${deploy.home}/WEB-INF/lib"/>
<copy todir="${deploy.home}/WEB-INF/lib" file="${xalan.jar}"/>
<copy todir="${deploy.home}/WEB-INF/lib" file="${xercesImpl.jar}"/>
<copy todir="${deploy.home}/WEB-INF/lib" file="${xml-apis.jar}"/>
<copy todir="${deploy.home}/WEB-INF/lib" file="${tidy.jar}"/>
Expand All @@ -547,11 +532,12 @@
<copy todir="${deploy.home}/WEB-INF/lib" file="${jdbc2_0-stdext.jar}"/>
<copy todir="${deploy.home}/WEB-INF/lib" file="${jdbcDriver.jar}"/>

<!-- This is Tomcat-specific! We need to think about a new property
<!-- There are Tomcat-specific! We need to think about a new property
that lets us specify the appropriate directory for other servers
-->
<copy todir="${server.home}/shared/lib" file="${portlet-api.jar}"/>
<copy todir="${server.home}/shared/lib" file="${pluto.jar}"/>
<copy todir="${server.home}/common/endorsed" file="${xalan.jar}"/>

<!-- This is Tomcat-specific and server name-specific!
We need to find out the best way to ensure cross-context
Expand Down Expand Up @@ -619,8 +605,7 @@
-->

<target name="javadoc" depends="compile"
description="Create Javadoc API documentation">
<target name="javadoc" description="Create Javadoc API documentation">

<mkdir dir="${dist.home}/docs/api"/>
<javadoc sourcepath="source"
Expand Down Expand Up @@ -908,7 +893,7 @@
The variable fragmentFile points to the XML file of the fragments definition
ant fragment -DfragmentFile=/properties/al/fragments.xml
ant pubfragments -DfragmentFile=/properties/al/fragments.xml
-->

Expand Down Expand Up @@ -1280,24 +1265,23 @@
-->


<target name="pubchan" description="Publishes channels" depends="compile">
<echo message="Invoking Channel Publisher Tool"/>

<property name="channel" value=" "/>
<java fork="true" dir="${basedir}" classname="org.jasig.portal.tools.chanpub.ChannelPublisher">
<classpath refid="compile.classpath"/>
<classpath>
<pathelement path="${build.home}/WEB-INF/classes"/>
<pathelement path="${build.home}/WEB-INF/classes"/>
<path refid="compile.classpath"/>
</classpath>
<arg value="-n"/>
<arg value="${channel}"/>
</java>
</target>



<!-- ===================== deployPortlet Target ========================= -->
<!-- ===================== deployPortletApp Target ========================= -->

<!--
Expand All @@ -1318,9 +1302,9 @@

<property name="portletApp" value=" "/>
<java fork="true" dir="${basedir}" classname="org.jasig.portal.container.deploy.Deployer">
<classpath refid="compile.classpath"/>
<classpath>
<pathelement path="${build.home}/WEB-INF/classes"/>
<path refid="compile.classpath"/>
</classpath>
<arg value="${deploy.home}/.."/>
<arg value="${portletApp}"/>
Expand Down
7 changes: 7 additions & 0 deletions docs/README
Expand Up @@ -53,6 +53,13 @@ The following ant command will deploy the documentation:
ant deploy


About HSQLDB
------------

Using an older version of hsqldb.jar with another version of the HSQLDB server could cause uPortal to hang.
See hsqldb.jar's entry in build.xml for documentation of exactly what version of hsqldb.jar is included with this release.


Copyright
---------

Expand Down
Binary file added docs/uPortal_architecture_overview.pdf
Binary file not shown.

0 comments on commit acf13ca

Please sign in to comment.