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 2004/04/09 20:54:13 UTC
cvs commit: jakarta-jetspeed/tutorial/xdocs downloading.xml
taylor 2004/04/09 11:54:13
Modified: tutorial/xdocs/6 lifecycle.xml deploy.xml
tutorial/xdocs/8 deploy.xml
tutorial/xdocs/9 deploy.xml
tutorial/xdocs/13 mvcintro.xml
tutorial project.xml project.properties
tutorial/xdocs/7 deploy.xml
tutorial/xdocs/1 skins.xml
tutorial/xdocs downloading.xml
Log:
- updated links to point to portals.apache.org
- set build to go off 1.5-dev
PR:
Obtained from:
Submitted by:
Reviewed by:
CVS: ----------------------------------------------------------------------
CVS: PR:
CVS: If this change addresses a PR in the problem report tracking
CVS: database, then enter the PR number(s) here.
CVS: Obtained from:
CVS: If this change has been taken from another system, such as NCSA,
CVS: then name the system in this line, otherwise delete it.
CVS: Submitted by:
CVS: If this code has been contributed to Apache by someone else; i.e.,
CVS: they sent us a patch or a new module, then include their name/email
CVS: address here. If this is your work then delete this line.
CVS: Reviewed by:
CVS: If we are doing pre-commit code reviews and someone else has
CVS: reviewed your changes, include their name(s) here.
CVS: If you have not had it reviewed then delete this line.
Revision Changes Path
1.2 +1 -1 jakarta-jetspeed/tutorial/xdocs/6/lifecycle.xml
Index: lifecycle.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/xdocs/6/lifecycle.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- lifecycle.xml 9 Apr 2004 16:22:14 -0000 1.1
+++ lifecycle.xml 9 Apr 2004 18:54:12 -0000 1.2
@@ -240,7 +240,7 @@
Think about the case where each user has his own page.
Since we are creating new portlets for every user in the system with her own page, if there are thousands of simultaneous users, we have the same portlet instantiated thousands of time.
It's a waste of memory. This approach was necessary in order to rectify a bug in Jetspeed's design: it shares all instance parameters across all instances.
- If you find this approach to be unsatisfactory, just override the <a href="http://jakarta.apache.org/jetspeed/api/org/apache/jetspeed/portal/portlets/AbstractPortlet.html#getHandle()">getHandle</a> method for your portlet and have its uniqueness based on the name of your portlet as shown in the commented out method in the tutorial example (its commented out in order for the tutorial example in 6.3 to work properly with multiple instances of the same portlet):
+ If you find this approach to be unsatisfactory, just override the <a href="http://portals.apache.org/jetspeed-1/apidocs/org/apache/jetspeed/portal/portlets/AbstractPortlet.html#getHandle()">getHandle</a> method for your portlet and have its uniqueness based on the name of your portlet as shown in the commented out method in the tutorial example (its commented out in order for the tutorial example in 6.3 to work properly with multiple instances of the same portlet):
</p>
<p>
1.2 +3 -1 jakarta-jetspeed/tutorial/xdocs/6/deploy.xml
Index: deploy.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/xdocs/6/deploy.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- deploy.xml 9 Apr 2004 17:39:00 -0000 1.1
+++ deploy.xml 9 Apr 2004 18:54:12 -0000 1.2
@@ -32,7 +32,9 @@
<p>
<source>
<![CDATA[
-ant deploy (or hotdeploy)
+maven deploy
+-- or --
+maven hotdeploy
]]>
</source>
</p>
1.2 +3 -1 jakarta-jetspeed/tutorial/xdocs/8/deploy.xml
Index: deploy.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/xdocs/8/deploy.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- deploy.xml 9 Apr 2004 03:35:14 -0000 1.1
+++ deploy.xml 9 Apr 2004 18:54:12 -0000 1.2
@@ -31,7 +31,9 @@
<p>
<source>
<![CDATA[
-ant deploy (or hotdeploy)
+maven deploy
+-- or --
+maven hotdeploy
]]>
</source>
</p>
1.2 +3 -1 jakarta-jetspeed/tutorial/xdocs/9/deploy.xml
Index: deploy.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/xdocs/9/deploy.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- deploy.xml 9 Apr 2004 03:01:01 -0000 1.1
+++ deploy.xml 9 Apr 2004 18:54:12 -0000 1.2
@@ -32,7 +32,9 @@
<p>
<source>
<![CDATA[
-ant deploy (or hotdeploy)
+maven deploy
+-- or --
+maven hotdeploy
]]>
</source>
</p>
1.5 +3 -3 jakarta-jetspeed/tutorial/xdocs/13/mvcintro.xml
Index: mvcintro.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/xdocs/13/mvcintro.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- mvcintro.xml 9 Apr 2004 14:55:44 -0000 1.4
+++ mvcintro.xml 9 Apr 2004 18:54:12 -0000 1.5
@@ -104,9 +104,9 @@
</p>
<p>
-The controller is your Velocity Action class. The base <a href="http://jakarta.apache.org/jetspeed/site/portlet_config_Velocity.html">VelocityPortlet</a> class should rarely have to be modified.
+The controller is your Velocity Action class. The base <a href="http://portals.apache.org/jetspeed-1/portlet_config_Velocity.html">VelocityPortlet</a> class should rarely have to be modified.
Your view is a Velocity template, which will generate the content of your portlet by pulling out dynamic model information from the Velocity context.
-The getContent method of the <a href="http://jakarta.apache.org/jetspeed/site/portlet_config_Velocity.html">VelocityPortlet</a> should never be edited.
+The getContent method of the <a href="http://portals.apache.org/jetspeed-1/portlet_config_Velocity.html">VelocityPortlet</a> should never be edited.
All content is generated by the template, as designed in our MVC design pattern.
</p>
@@ -160,7 +160,7 @@
<p>
Velocity portlets are really about dynamic content.
If you have static content, there is no real benefit to using a Velocity portlet; take a look at one of the static content generation portlets such as the
-<a href="http://jakarta.apache.org/jetspeed/site/portlet_config_HTML.html">HTMLPortlet</a> instead.
+<a href="http://portals.apache.org/jetspeed-1/portlet_config_HTML.html">HTMLPortlet</a> instead.
The basic function of Velocity is really very simple, it substitutes live Java objects into a Velocity template.
There is an online tutorial with great examples <a href="http://jakarta.apache.org/velocity/user-guide.html#What%20is%20Velocity?">here</a>.
</p>
1.7 +2 -2 jakarta-jetspeed/tutorial/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/project.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- project.xml 8 Apr 2004 23:14:49 -0000 1.6
+++ project.xml 9 Apr 2004 18:54:12 -0000 1.7
@@ -106,7 +106,7 @@
<war.bundle.jar>false</war.bundle.jar>
<dist.native.name>jetspeed-${jetspeed.dist.version}</dist.native.name>
</properties>
- <url>http://jakarta.apache.org/jetspeed/</url>
+ <url>http://portals.apache.org/jetspeed-1/</url>
<type>distribution</type>
<jar>jetspeed-${jetspeed.dist.version}.zip</jar>
</dependency>
@@ -116,7 +116,7 @@
<properties>
<war.bundle.jar>true</war.bundle.jar>
</properties>
- <url>http://jakarta.apache.org/jetspeed/</url>
+ <url>http://portals.apache.org/jetspeed-1/</url>
</dependency>
</dependencies>
<dependencies>
1.8 +1 -1 jakarta-jetspeed/tutorial/project.properties
Index: project.properties
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/project.properties,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- project.properties 9 Apr 2004 05:45:44 -0000 1.7
+++ project.properties 9 Apr 2004 18:54:12 -0000 1.8
@@ -59,5 +59,5 @@
maven.merge.properties = JetspeedResources,JetspeedSecurity,TurbineResources,Torque
-jetspeed.dist.version = 1.5
+jetspeed.dist.version = 1.5-dev
1.2 +3 -1 jakarta-jetspeed/tutorial/xdocs/7/deploy.xml
Index: deploy.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/xdocs/7/deploy.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- deploy.xml 9 Apr 2004 14:54:17 -0000 1.1
+++ deploy.xml 9 Apr 2004 18:54:12 -0000 1.2
@@ -31,7 +31,9 @@
<p>
<source>
<![CDATA[
-ant deploy (or hotdeploy)
+maven deploy
+-- or --
+maven hotdeploy
]]>
</source>
</p>
1.3 +1 -1 jakarta-jetspeed/tutorial/xdocs/1/skins.xml
Index: skins.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/xdocs/1/skins.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- skins.xml 9 Apr 2004 05:42:47 -0000 1.2
+++ skins.xml 9 Apr 2004 18:54:13 -0000 1.3
@@ -62,7 +62,7 @@
The default skin facilitates quickly creating a site look and feel with minimal effort.
</p>
<p>
-See the <a href='http://jakarta.apache.org/jetspeed/site/config_skin.html'>Jetspeed Skin documentation</a>
+See the <a href='http://portals.apache.org/jetspeed-1/config_skin.html'>Jetspeed Skin documentation</a>
for all available skin parameters.
</p>
<p>
1.4 +1 -1 jakarta-jetspeed/tutorial/xdocs/downloading.xml
Index: downloading.xml
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/tutorial/xdocs/downloading.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- downloading.xml 9 Apr 2004 05:42:48 -0000 1.3
+++ downloading.xml 9 Apr 2004 18:54:13 -0000 1.4
@@ -31,7 +31,7 @@
<br/><br/>
To checkout from the CVS head, follow the instructions here:
<br/><br/>
-<a href='http://jakarta.apache.org/jetspeed/site/install.html'>CVS Head</a>
+<a href='http://portals.apache.org/jetspeed-1/install.html'>CVS Head</a>
<br/><br/>
and then build the distribution target (maven dist:install).
<br/><br/>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org