You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by ta...@apache.org on 2005/04/20 06:35:58 UTC
cvs commit: jakarta-jetspeed/xdocs/stylesheets project.xml
taylor 2005/04/19 21:35:58
Modified: xdocs install.xml usejetspeed.xml messaging.xml
features.xml
tutorial/xdocs/6 initparams.xml
xdocs/stylesheets project.xml
Added: xdocs fusion.xml
Log:
start of fusion docs, jetspeed cluster, 1.6 updates
Revision Changes Path
1.36 +1 -1 jakarta-jetspeed/xdocs/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/xdocs/install.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- install.xml 22 Apr 2004 19:11:10 -0000 1.35
+++ install.xml 20 Apr 2005 04:35:58 -0000 1.36
@@ -53,7 +53,7 @@
<section name="Requirements">
<ul>
<li>
-A Java Servlet Engine/Container. Must be compatible with the Servlet 2.2 or Servlet 2.3 API.<br/>
+A Java Servlet Engine/Container. Must be compatible with the Servlet 2.3 API.<br/>
Note: Jetspeed is developed under Tomcat which is available from
<a href="http://jakarta.apache.org/tomcat">http://jakarta.apache.org/tomcat</a>
</li>
1.26 +1 -1 jakarta-jetspeed/xdocs/usejetspeed.xml
Index: usejetspeed.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/xdocs/usejetspeed.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- usejetspeed.xml 14 Mar 2005 16:24:46 -0000 1.25
+++ usejetspeed.xml 20 Apr 2005 04:35:58 -0000 1.26
@@ -53,7 +53,7 @@
</tr>
<tr>
<td>
- <a href="http://www.askted.com.au/askted/">http://www.askted.com.au/askted/</a>
+ <a href="http://www.askted.com.au">http://www.askted.com.au/askted/</a>
</td>
<td>Guides, news and reviews on whats happening in Western Australia.</td>
<td>1.5</td>
1.2 +3 -2 jakarta-jetspeed/xdocs/messaging.xml
Index: messaging.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/xdocs/messaging.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- messaging.xml 4 Aug 2004 01:24:51 -0000 1.1
+++ messaging.xml 20 Apr 2005 04:35:58 -0000 1.2
@@ -16,10 +16,11 @@
-->
<document>
<properties>
- <title>Jetspeed Messaging</title>
- <subtitle>Messaging Support in Jetspeed</subtitle>
+ <title>Jetspeed Cluster</title>
+ <subtitle>Cluster and JMS Messaging Support in Jetspeed</subtitle>
<authors>
<person name="Jeremy Ford" email="jford@apache.org"/>
+ <person name="David Sean Taylor" email="taylor@apache.org"/>
</authors>
</properties>
<body>
1.9 +3 -1 jakarta-jetspeed/xdocs/features.xml
Index: features.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/xdocs/features.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- features.xml 17 Mar 2004 21:27:50 -0000 1.8
+++ features.xml 20 Apr 2005 04:35:58 -0000 1.9
@@ -28,7 +28,7 @@
<section name="Features">
<p>Jetspeed has support for the following features:</p>
<ul>
- <li>Soon to standardize on a Java Portlet API specification</li>
+ <li>JSR-168 Support of Java Portlet API specification (Fusion)</li>
<li>Template-based layouts including JSP and Velocity</li>
<li>Supports remote XML content feeds via Open Content Syndication
</li>
@@ -56,6 +56,8 @@
<li>PSML can be stored in a Database.</li>
<li>User, group, role and permission administration via Jetspeed security portlets.</li>
<li>Role-based security access to portlets.</li>
+ <li>Jetspeed Cluster and Messaging (JMS Support): for running Jetspeed as a clustered portal.</li>
+ <li>Generic View Processors to render content uniformly in your Java code to JSP, XSLT, or Velocity.</li>
</ul>
</section>
</body>
1.1 jakarta-jetspeed/xdocs/fusion.xml
Index: fusion.xml
===================================================================
<?xml version="1.0"?>
<!--
Copyright 2004 The Apache Software Foundation
Licensed 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>JSR-168</title>
<subtitle>Fusion - JSR 168 Support in Jetspeed-1</subtitle>
<authors>
<person name="David S. Taylor" email="david@bluesunrise.com"/>
</authors>
</properties>
<body>
<section name="Overview">
<subsection name="What is Fusion?">
<p>
As of Jetspeed 1.6, Jetspeed-1 now supports the
<a href="http://www.jcp.org/aboutJava/communityprocess/review/jsr168/">Java Portlet API Standard</a>.
The specification and standard are also known as JSR-168, or the Portlet API.
Note that Fusion is an optional feature of Jetspeed 1.6. You must specifically build Fusion, or
download the Fusion distribution as it is not included in the default distribution or
in the default build.
</p>
<p>
In the summer of 2004, the Jetspeed Fusion project was developed.
Fusion enables Jetspeed-1 to run standard Java Portlet applications in Jetspeed-1.
This was made possible by leveraging the component architecture in Jetspeed-2.
The Jetspeed-2 portal engine is compliant with the Java Portlet Standard.
Fusion embeds the Jetspeed-2 portal engine inside of the Jetspeed-1 portal.
</p>
</subsection>
<subsection name="Running Jetspeed Fusion">
<p>Jetspeed Fusion does require more configuration than a plain old Jetspeed 1.6 installation.
This is because of the nature of the Portlet API: portlet applications are deployed as WAR files
and run in their web application, separate from the portal. With Fusion, we need to install several
support jars into the common or shared class path area of your particular application server. The 1.6
release comes with a packaged Fusion and Tomcat 5 combination, ready to run. If you are installing to your
own application server, you will need some extra setup for Fusion to run. In this example, we are use Tomcat 5.
The following jars need to be placed into Tomcat's shared/lib directory:
</p>
<table>
<tr>
<th>JAR</th>
<th>Description</th>
</tr>
<tr>
<td>jetspeed-api-*</td>
<td>The Jetspeed-2 API interfaces</td>
</tr>
<tr>
<td>pluto-*</td>
<td>The Pluto Container implementation</td>
</tr>
<tr>
<td>portlet-api-*</td>
<td>The Portlet API interfaces</td>
</tr>
<tr>
<td>jetspeed-commons-*</td>
<td>The Jetspeed-2 Cross Context support classes</td>
</tr>
<tr>
<td>jetspeed-commons-*</td>
<td>The Jetspeed-2 Cross Context support classes</td>
</tr>
<tr>
<td>portals-bridges-commons-*</td>
<td>The Portals Bridges support classes</td>
</tr>
</table>
<i>The <b>*</b> denotes a particular version, such as 2.0-M2 for example.</i>
<p>See the section on building from source below for details on how to automate the process.</p>
</subsection>
<subsection name="Deploying Portlet Applications">
<p>
Deploying a portlet application to Jetspeed is very easy. Make sure that Jetspeed is running in an application server.
In this example, we will assume its Tomcat.
All you need to do is drop the portlet application archive (WAR) file into the Jetspeed deploy directory,
and Jetspeed handles the rest automatically. This feature is called <i>Auto Deployment</i>.
</p>
<p>
When you are ready to deploy a new portlet application to the server,
simply copy the war file into the Jetspeed-1 Auto Deployment directory located under
</p>
<source test=""><![CDATA[
${TOMCAT_HOME}/webapps/jetspeed/WEB-INF/deploy/
]]></source>
<p>
Jetspeed will automatically pick up and deploy the application within 10 seconds or so.
You can then go to the portlet customizer, and select the portlets that you deployed and place them
in your portal. From the Customizer Add Portlet page, there are two filters to help you
find JSR-168 standard portlets: <b>JSR-168</b> and <b>Portlet API</b>. Once you've selected the portlets
in the customizer, you can then start using the portlets immediately.
</p>
</subsection>
<subsection name="Running Fusion on App Servers">
<p>
Fusion should run on any application server. We have a Wiki page with the status of successfully installed
application servers and the instructions on how to do so here: <a href="http://wiki.apache.org/portals/Jetspeed2/Fusion">Fusion Wiki</a>
</p>
</subsection>
<subsection name="Building Fusion">
<p>
The instructions here are for those who would like to build Fusion from source.
By default, Jetspeed 1.6 builds without Fusion. To build Fusion, enable the build by
setting this property in your $HOME/build.properties:
</p>
<source test=""><![CDATA[
org.apache.jetspeed.fusion = true
]]></source>
</subsection>
</section>
</body>
</document>
1.2 +2 -2 jakarta-jetspeed/tutorial/xdocs/6/initparams.xml
Index: initparams.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/xdocs/6/initparams.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- initparams.xml 9 Apr 2004 17:02:31 -0000 1.1
+++ initparams.xml 20 Apr 2005 04:35:58 -0000 1.2
@@ -31,7 +31,7 @@
Attributes are defined in a PSML file. Init Parameters are associated with all portlets
of a given class and are read only. Attributes are associated with only one instance of
a portlet class on a given PSML page, and can be modified and persisted. Given our example
-portlet, we have the Init Parameter named 'version', which is set to the value '1.4b4'.
+portlet, we have the Init Parameter named 'version', which is set to the value '1.6'.
We also have two instances of the same portlet on our page.
Each of these portlets instances have the same parameter defined on the same PSML page,
called 'city' with the value of 'Tokyo' and 'Sidney'.
@@ -44,7 +44,7 @@
</p>
<source>
<![CDATA[
- <parameter name="version" value="1.4b4" hidden="false"/>
+ <parameter name="version" value="1.6" hidden="false"/>
]]>
</source>
<p>
1.30 +3 -1 jakarta-jetspeed/xdocs/stylesheets/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/xdocs/stylesheets/project.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- project.xml 4 Jan 2005 17:10:11 -0000 1.29
+++ project.xml 20 Apr 2005 04:35:58 -0000 1.30
@@ -44,8 +44,10 @@
<item name="Portlet Catalog" href="/catalog.html"/>
</menu>
<menu name="Components">
+ <item name="JSR-168 Portlets" href="/fusion.html"/>
<item name="Registry" href="/registry.html"/>
<item name="Security" href="/security.html"/>
+ <item name="View Processors" href="/viewprocessors.html"/>
<item name="Syndication" href="/content-syndication.html"/>
<item name="WAP" href="/wap.html"/>
<item name="Customization" href="/customizer.html"/>
@@ -53,7 +55,7 @@
<item name="PSML" href="/psml.html"/>
<item name="Forwards" href="/forwards.html"/>
<item name="Database" href="/database.html"/>
- <item name="JMS MessagingService" href="/messaging.html"/>
+ <item name="Jetspeed Cluster (JMS)" href="/messaging.html"/>
</menu>
<menu name="Translated">
<item name="Japanese (Web)" href="http://jakarta.terra-intl.com/jetspeed/"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org