portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From a..@apache.org
Subject svn commit: r725977 [47/48] - in /portals/jetspeed-2/portal/trunk: ./ app-servers/security/jboss/src/java/META-INF/jboss-secsvc/ app-servers/security/jboss/src/java/org/apache/jetspeed/appservers/security/jboss/ applications/jetspeed/src/main/javascrip...
Date Fri, 12 Dec 2008 12:07:04 GMT
Modified: portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/page-decoration.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/page-decoration.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/page-decoration.xml (original)
+++ portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/page-decoration.xml Fri Dec 12 04:06:29 2008
@@ -1,198 +1,198 @@
-<?xml version="1.0"?>
-<!--
+<?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>Page Decorators</title>
-		<subtitle>Customizing Page Decorators</subtitle>
-		<authors>
-			<person name="David Sean Taylor" email="taylor@apache.org" />
-		</authors>
-	</properties>
-	<body>
-    <section name="Page Decorators">
-      <p> 
-      Each Jetspeed page can be associated with a different page decoration. Page decorations
-      control some important aspect of a portal page:
-      <ul>
-      <li>The colors, images, CSS styles that skin this page</li>
-      <li>The header portion of the page</li>
-      <li>The page margins</li>
-      <li>The footer portion of the page</li>
-      <li>Menus displayed on the page</li>
-      <li>Action buttons displayed on the window</li>      
-      </ul>
-      Decorators do not control the placement of portlets. That is handled by layouts.
-      Jetspeed comes with several page decorations out of the box. The default page decorator for 
-      most pages is called <i>tigris</i>. It looks like this:
-      </p>
-      <img src="../images/tigris-page.png"/>
-      <p>
-      We are going to create a new decorator for this tutorial.
-      This new decorator can be copied into our project from the <i>/JetspeedTutorial/resources/decorations/layout/express-page/</i> directory.
-      This will save you the trouble of creating all the logo images and CSS definitions.
-      </p>
-	 <source>
-	 <![CDATA[
-# Linux	 
-cd /JetspeedTraining/workspace/jetexpress
-mkdir portal/src/webapp/decorations/layout/express-page
-cp -r ../../resources/decorations/layout/express-page/* portal/src/webapp/decorations/layout/express-page/
-
-# Windows
-cd \JetspeedTraining\workspace\jetexpress
-mkdir portal\src\webapp\decorations\layout\express-page
-xcopy /s ..\..\resources\decorations\layout\express-page\* portal\src\webapp\decorations\layout\express-page
-     ]]>
-     </source>	  	  
-    <subsection name="The Header">
-    <p>
-    Open up the <i>decorations/layout/express-page/header.vm</i>
-    This is a Velocity template, very much like JSP but simpler, with no Java compilation required.
-    Jetspeed does support JSP-based decorators. However no one has contributed one yet.
-    We could spend a lot of time teaching you about all the macros available.
-    But lets just concentrate on changing the logos first.
-    Scroll down to the banner content. Here we add our new left-hand side logo:
-    </p>
-	 <source>
-	 <![CDATA[    
-#GetPageResource('images/blueSunrisePicture.gif')    	 
-     ]]>
-     </source>	  	  
-     <p>
-     We've added a few more custom images, one in the center area of the banner:
-     </p>
-	 <source>
-	 <![CDATA[    
-<img src="#GetPageResource('images/BlueSunriseTextTahoma.gif')" height="29" width="165">	 
-     ]]>
-     </source>	  	  
-     <p>
-     and one more in the right area of the banner:
-     </p>
-	 <source>
-	 <![CDATA[    
-<img src="#GetPageResource('images/RisingEdgeSlogan.gif')" height="28" width="300">
-     ]]>
-     </source>	  	  
-     <p>
-     <i>#GetPageResource</i> is a Velocity macro. It retrieves a resource (image, CSS, HTML) from
-     the decoration folder, relative  to the root of the express-page decoration folder.
-     Besides the images, the header.vm is pretty much the same as Tigris.
-     In fact we simply cut and  paste the Tigris decorator to get us started.
-     This gives you a good  start of customizing the page.
-     </p>
-    </subsection>
-    <subsection name="Velocity Variables">    
-    <p>
-    Velocity makes several variables about the context of a decoration available for dynamic substition of menus and content:
-    </p>
-    <table>
-    <tr>
-    <th>Variable</th>
-    <th>Desc</th>    
-    <th>Usage</th>
-    </tr>
-    <tr>
-    <td>$layoutDecoration</td>
-    <td>Retrieve layout content from the decoration dir</td>
-    <td>$layoutDecoration.getResource("decorator-macros.vm")</td>
-    </tr>
-    <tr>
-    <td>$site</td>
-    <td>Retrieve menus by name</td>
-    <td>$site.getMenu("pages")</td>
-    </tr>
-    </table>
-    </subsection>
-    <subsection name="Menus">   
-     <p>
-     The remainder of the page is HTML markup mixed in with some important macros
-     for displaying Jetspeed Menus. <i>Jetspeed Menus</i> are build from a collection of portal resources
-     known as the <i>Portal Site</i>. The portal site is a content tree (like a file system) of portal
-     resources. The site can be stored in the file system or in a database. Resources can be a page,
-     folder, or link.  Lets look at some of the available macros for displaying menus on your page.
-     </p>	     
-    <p>
-    The $site always has the following menus available to you at any time:
-    <table>
-    <tr>
-    <th>Menu</th>
-    <th>Desc</th>
-    </tr>
-    <tr>
-    <td>pages</td>
-    <td>relative pages menu of pages in the current folder. Used to define the page tabs above the portal.</td>
-    </tr>
-    <tr>
-    <td>breadcrumbs</td>
-    <td>paths to page used to provide history links below the page tabs</td>
-    </tr>
-    <tr>
-    <td>navigations</td>
-    <td>relative subfolders and root level links menu used to define the navigation pane beside the portal.</td>
-    </tr>
-    <tr>
-    <td>back</td>
-    <td>parent folder menu used to define the single "back" link above the portal page tabs.</td>
-    </tr>
-    </table>
-    You can also define your own menus (not covered in this tutorial).
-    </p>
-	<p>
-	There are some helper macros for creating different styles of menus.
-	The macros are defined in the decorator-macros.vm file:	     
-     <table>
-     <tr>
-     <th>Macro</th>
-     <th>Decription</th>     
-     </tr>
-     <tr>
-     <td>#includeTabsNavigation($someMenu $LEFT_TO_RIGHT)</td>
-     <td>Displays a menu in a vertical tabbed navigation style.</td>
-     </tr>
-     <tr>
-     <td>#includeLinksNavigation($breadCrumb $LEFT_TO_RIGHT "" $BREADCRUMBS_STYLE "")</td>
-     <td>Displays a menu of links according to a given style.</td>
-     </tr>
-     <tr>
-     <td>#includeNestedLinksWithIconNavigation($standardNavs $TOP_TO_BOTTOM)</td>
-     <td>Displays a nested top-to-bottom menu navigation of folders, links, and pages.</td>
-     </tr>
-     <tr>
-     <td>#PageActionBar()</td>
-     <td>Not a menu, but the available actions (edit, view, help, print...) for this page</td>
-     </tr>
-     </table>
-     </p>
-    </subsection>    	     
-    <subsection name="The Footer">
-    <p>
-    Open up the <i>decorations/layout/express-page/footer.vm</i>
-    </p>
-	 <source>
-	 <![CDATA[    
-<img src="#GetPageResource('images/jetspeed-powered.gif')" alt="Jetspeed 2 Powered" border="0" />
-     ]]>
-     </source>	  	  
-    </subsection>    
-	  <p>
-	    <a href='customizing-overview.html'>Previous</a> <a href='portlet-decoration.html'>Next</a>
-	  </p>	      
- </section>	  
-</body>
+	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>Page Decorators</title>
+		<subtitle>Customizing Page Decorators</subtitle>
+		<authors>
+			<person name="David Sean Taylor" email="taylor@apache.org" />
+		</authors>
+	</properties>
+	<body>
+    <section name="Page Decorators">
+      <p> 
+      Each Jetspeed page can be associated with a different page decoration. Page decorations
+      control some important aspect of a portal page:
+      <ul>
+      <li>The colors, images, CSS styles that skin this page</li>
+      <li>The header portion of the page</li>
+      <li>The page margins</li>
+      <li>The footer portion of the page</li>
+      <li>Menus displayed on the page</li>
+      <li>Action buttons displayed on the window</li>      
+      </ul>
+      Decorators do not control the placement of portlets. That is handled by layouts.
+      Jetspeed comes with several page decorations out of the box. The default page decorator for 
+      most pages is called <i>tigris</i>. It looks like this:
+      </p>
+      <img src="../images/tigris-page.png"/>
+      <p>
+      We are going to create a new decorator for this tutorial.
+      This new decorator can be copied into our project from the <i>/JetspeedTutorial/resources/decorations/layout/express-page/</i> directory.
+      This will save you the trouble of creating all the logo images and CSS definitions.
+      </p>
+	 <source>
+	 <![CDATA[
+# Linux	 
+cd /JetspeedTraining/workspace/jetexpress
+mkdir portal/src/webapp/decorations/layout/express-page
+cp -r ../../resources/decorations/layout/express-page/* portal/src/webapp/decorations/layout/express-page/
+
+# Windows
+cd \JetspeedTraining\workspace\jetexpress
+mkdir portal\src\webapp\decorations\layout\express-page
+xcopy /s ..\..\resources\decorations\layout\express-page\* portal\src\webapp\decorations\layout\express-page
+     ]]>
+     </source>	  	  
+    <subsection name="The Header">
+    <p>
+    Open up the <i>decorations/layout/express-page/header.vm</i>
+    This is a Velocity template, very much like JSP but simpler, with no Java compilation required.
+    Jetspeed does support JSP-based decorators. However no one has contributed one yet.
+    We could spend a lot of time teaching you about all the macros available.
+    But lets just concentrate on changing the logos first.
+    Scroll down to the banner content. Here we add our new left-hand side logo:
+    </p>
+	 <source>
+	 <![CDATA[    
+#GetPageResource('images/blueSunrisePicture.gif')    	 
+     ]]>
+     </source>	  	  
+     <p>
+     We've added a few more custom images, one in the center area of the banner:
+     </p>
+	 <source>
+	 <![CDATA[    
+<img src="#GetPageResource('images/BlueSunriseTextTahoma.gif')" height="29" width="165">	 
+     ]]>
+     </source>	  	  
+     <p>
+     and one more in the right area of the banner:
+     </p>
+	 <source>
+	 <![CDATA[    
+<img src="#GetPageResource('images/RisingEdgeSlogan.gif')" height="28" width="300">
+     ]]>
+     </source>	  	  
+     <p>
+     <i>#GetPageResource</i> is a Velocity macro. It retrieves a resource (image, CSS, HTML) from
+     the decoration folder, relative  to the root of the express-page decoration folder.
+     Besides the images, the header.vm is pretty much the same as Tigris.
+     In fact we simply cut and  paste the Tigris decorator to get us started.
+     This gives you a good  start of customizing the page.
+     </p>
+    </subsection>
+    <subsection name="Velocity Variables">    
+    <p>
+    Velocity makes several variables about the context of a decoration available for dynamic substition of menus and content:
+    </p>
+    <table>
+    <tr>
+    <th>Variable</th>
+    <th>Desc</th>    
+    <th>Usage</th>
+    </tr>
+    <tr>
+    <td>$layoutDecoration</td>
+    <td>Retrieve layout content from the decoration dir</td>
+    <td>$layoutDecoration.getResource("decorator-macros.vm")</td>
+    </tr>
+    <tr>
+    <td>$site</td>
+    <td>Retrieve menus by name</td>
+    <td>$site.getMenu("pages")</td>
+    </tr>
+    </table>
+    </subsection>
+    <subsection name="Menus">   
+     <p>
+     The remainder of the page is HTML markup mixed in with some important macros
+     for displaying Jetspeed Menus. <i>Jetspeed Menus</i> are build from a collection of portal resources
+     known as the <i>Portal Site</i>. The portal site is a content tree (like a file system) of portal
+     resources. The site can be stored in the file system or in a database. Resources can be a page,
+     folder, or link.  Lets look at some of the available macros for displaying menus on your page.
+     </p>	     
+    <p>
+    The $site always has the following menus available to you at any time:
+    <table>
+    <tr>
+    <th>Menu</th>
+    <th>Desc</th>
+    </tr>
+    <tr>
+    <td>pages</td>
+    <td>relative pages menu of pages in the current folder. Used to define the page tabs above the portal.</td>
+    </tr>
+    <tr>
+    <td>breadcrumbs</td>
+    <td>paths to page used to provide history links below the page tabs</td>
+    </tr>
+    <tr>
+    <td>navigations</td>
+    <td>relative subfolders and root level links menu used to define the navigation pane beside the portal.</td>
+    </tr>
+    <tr>
+    <td>back</td>
+    <td>parent folder menu used to define the single "back" link above the portal page tabs.</td>
+    </tr>
+    </table>
+    You can also define your own menus (not covered in this tutorial).
+    </p>
+	<p>
+	There are some helper macros for creating different styles of menus.
+	The macros are defined in the decorator-macros.vm file:	     
+     <table>
+     <tr>
+     <th>Macro</th>
+     <th>Decription</th>     
+     </tr>
+     <tr>
+     <td>#includeTabsNavigation($someMenu $LEFT_TO_RIGHT)</td>
+     <td>Displays a menu in a vertical tabbed navigation style.</td>
+     </tr>
+     <tr>
+     <td>#includeLinksNavigation($breadCrumb $LEFT_TO_RIGHT "" $BREADCRUMBS_STYLE "")</td>
+     <td>Displays a menu of links according to a given style.</td>
+     </tr>
+     <tr>
+     <td>#includeNestedLinksWithIconNavigation($standardNavs $TOP_TO_BOTTOM)</td>
+     <td>Displays a nested top-to-bottom menu navigation of folders, links, and pages.</td>
+     </tr>
+     <tr>
+     <td>#PageActionBar()</td>
+     <td>Not a menu, but the available actions (edit, view, help, print...) for this page</td>
+     </tr>
+     </table>
+     </p>
+    </subsection>    	     
+    <subsection name="The Footer">
+    <p>
+    Open up the <i>decorations/layout/express-page/footer.vm</i>
+    </p>
+	 <source>
+	 <![CDATA[    
+<img src="#GetPageResource('images/jetspeed-powered.gif')" alt="Jetspeed 2 Powered" border="0" />
+     ]]>
+     </source>	  	  
+    </subsection>    
+	  <p>
+	    <a href='customizing-overview.html'>Previous</a> <a href='portlet-decoration.html'>Next</a>
+	  </p>	      
+ </section>	  
+</body>
 </document>
\ No newline at end of file

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/page-decoration.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/portlet-decoration.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/portlet-decoration.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/portlet-decoration.xml (original)
+++ portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/portlet-decoration.xml Fri Dec 12 04:06:29 2008
@@ -1,71 +1,71 @@
-<?xml version="1.0"?>
-<!--
+<?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>Portlet Decorators</title>
-		<subtitle>Customizing PortletDecorators</subtitle>
-		<authors>
-			<person name="David Sean Taylor" email="taylor@apache.org" />
-		</authors>
-	</properties>
-	<body>
-    <section name="Portlet Decorators">
-      <p> 
-      Each Jetspeed portlet window on a page can be associated with a different portlet decoration. 
-      Portlet decorations control some important aspect of a portlet window:
-      <ul>
-      <li>The colors, images, CSS styles that skin this window</li>
-      <li>The title portion of the portlet</li>
-      <li>The borders of the window</li>
-      <li>Action buttons displayed on the window</li>
-      </ul>      
-      Jetspeed comes with several portlet decorations out of the box. The default page decorator for 
-      most pages is called <i>tigris</i>. It looks like this:
-      </p>
-      <img src="../images/tigris-portlet.png"/>
-      <p>
-      We are going to create a new decorator for this tutorial.
-      This new decorator can be copied into our project from the <i>/JetspeedTutorial/resources/decorations/portlet/express-portlet/</i> directory.
-      This will save you the trouble of creating all the logo images and CSS definitions.
-      </p>
-	 <source>
-	 <![CDATA[
-# Linux	 
-cd /JetspeedTraining/workspace/jetexpress
-mkdir portal/src/webapp/decorations/portlet/express-portlet
-cp -r ../../resources/decorations/portlet/express-portlet/* portal/src/webapp/decorations/portlet/express-portlet/
-
-# Windows
-cd \JetspeedTraining\workspace\jetexpress
-mkdir portal\src\webapp\decorations\portlet\express-portlet
-xcopy /s ..\..\resources\decorations\portlet\express-portlet\* portal\src\webapp\decorations\portlet\express-portlet
-     ]]>
-     </source>	  	  
-     <p>
-     We are going to skip over the intricate details of portlet decorators, as page decorators are much more 
-     important, as they set your organization's branding. Whereas the standard window decorators are good 
-     enough for getting you started. Go ahead and review the content of our custom portlet decorator.
-     You will see that the directory layout is the same as for page decorators. The decorator simply
-     creates a new color variation on an existing window decorator.
-	  </p>	      
-	  <p>
-	    <a href='page-decoration.html'>Previous</a> <a href='desktop-theme.html'>Next</a>
-	  </p>	      	  
- </section>	  
-</body>
+	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>Portlet Decorators</title>
+		<subtitle>Customizing PortletDecorators</subtitle>
+		<authors>
+			<person name="David Sean Taylor" email="taylor@apache.org" />
+		</authors>
+	</properties>
+	<body>
+    <section name="Portlet Decorators">
+      <p> 
+      Each Jetspeed portlet window on a page can be associated with a different portlet decoration. 
+      Portlet decorations control some important aspect of a portlet window:
+      <ul>
+      <li>The colors, images, CSS styles that skin this window</li>
+      <li>The title portion of the portlet</li>
+      <li>The borders of the window</li>
+      <li>Action buttons displayed on the window</li>
+      </ul>      
+      Jetspeed comes with several portlet decorations out of the box. The default page decorator for 
+      most pages is called <i>tigris</i>. It looks like this:
+      </p>
+      <img src="../images/tigris-portlet.png"/>
+      <p>
+      We are going to create a new decorator for this tutorial.
+      This new decorator can be copied into our project from the <i>/JetspeedTutorial/resources/decorations/portlet/express-portlet/</i> directory.
+      This will save you the trouble of creating all the logo images and CSS definitions.
+      </p>
+	 <source>
+	 <![CDATA[
+# Linux	 
+cd /JetspeedTraining/workspace/jetexpress
+mkdir portal/src/webapp/decorations/portlet/express-portlet
+cp -r ../../resources/decorations/portlet/express-portlet/* portal/src/webapp/decorations/portlet/express-portlet/
+
+# Windows
+cd \JetspeedTraining\workspace\jetexpress
+mkdir portal\src\webapp\decorations\portlet\express-portlet
+xcopy /s ..\..\resources\decorations\portlet\express-portlet\* portal\src\webapp\decorations\portlet\express-portlet
+     ]]>
+     </source>	  	  
+     <p>
+     We are going to skip over the intricate details of portlet decorators, as page decorators are much more 
+     important, as they set your organization's branding. Whereas the standard window decorators are good 
+     enough for getting you started. Go ahead and review the content of our custom portlet decorator.
+     You will see that the directory layout is the same as for page decorators. The decorator simply
+     creates a new color variation on an existing window decorator.
+	  </p>	      
+	  <p>
+	    <a href='page-decoration.html'>Previous</a> <a href='desktop-theme.html'>Next</a>
+	  </p>	      	  
+ </section>	  
+</body>
 </document>
\ No newline at end of file

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/02/portlet-decoration.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/build-it.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/build-it.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/build-it.xml (original)
+++ portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/build-it.xml Fri Dec 12 04:06:29 2008
@@ -1,71 +1,71 @@
-<?xml version="1.0"?>
-<!--
+<?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>Building and Deploying</title>
-    <subtitle>Building and Deploying the Portlet Application</subtitle>
-	<authors>
-		<person name="David Sean Taylor" email="taylor@apache.org" />
-	</authors>
-  </properties>
-  <body>
-    <section name="Building and Deploying the Portlet Application">
-      <p>      
-       Now that you have generated a portlet app named <b>express-demo</b>, we are ready to build the portal.
-       We are going to build the portal from the command line:
-      </p>
-	 <source>
-	 <![CDATA[
-# Linux	 
-cd /JetspeedTraining/workspace/jetexpress/applications/express-demo
-
-# Windows
-cd \JetspeedTraining\workspace\jetexpress\applications\express-demo
-
-mvn 
-     ]]>
-	</source> 
-      <p>
-      This builds a portlet application war file name <i>express-demo-1.0.war</i>.
-      This war file is found under <i>target</i> directory. It is a standard JSR-168 portlet application distribution.
-      </p>
-      <p>
-      Now that we've built and deployed the portal, lets start up the application server (if its not already started).
-      While the app server is running, we can drop in the portlet application.
-      </p>	
-	 <source>
-	 <![CDATA[
-# Linux	 
-cd /JetspeedTraining/workspace/jetexpress/applications/express-demo
-cp target/express-demo-1.0.war /JetspeedTraining/tomcat-express/webapps/express-demo.war
-
-# Windows
-cd \JetspeedTraining\workspace\jetexpress\applications\express-demo
-copy target\express-demo-1.0.war \JetspeedTraining\tomcat-express\webapps\express-demo.war
-
-     ]]>
-	</source> 
-	<p>This will deploy your portlet application. Next, lets see how to add your new portlets to a page.
-	</p>      
-	  <p>
-	    <a href='portlet-app.html'>Previous</a> <a href='pages.html'>Next</a>
-	  </p>            
-    </section>
-  </body>
-</document>
-
+  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>Building and Deploying</title>
+    <subtitle>Building and Deploying the Portlet Application</subtitle>
+	<authors>
+		<person name="David Sean Taylor" email="taylor@apache.org" />
+	</authors>
+  </properties>
+  <body>
+    <section name="Building and Deploying the Portlet Application">
+      <p>      
+       Now that you have generated a portlet app named <b>express-demo</b>, we are ready to build the portal.
+       We are going to build the portal from the command line:
+      </p>
+	 <source>
+	 <![CDATA[
+# Linux	 
+cd /JetspeedTraining/workspace/jetexpress/applications/express-demo
+
+# Windows
+cd \JetspeedTraining\workspace\jetexpress\applications\express-demo
+
+mvn 
+     ]]>
+	</source> 
+      <p>
+      This builds a portlet application war file name <i>express-demo-1.0.war</i>.
+      This war file is found under <i>target</i> directory. It is a standard JSR-168 portlet application distribution.
+      </p>
+      <p>
+      Now that we've built and deployed the portal, lets start up the application server (if its not already started).
+      While the app server is running, we can drop in the portlet application.
+      </p>	
+	 <source>
+	 <![CDATA[
+# Linux	 
+cd /JetspeedTraining/workspace/jetexpress/applications/express-demo
+cp target/express-demo-1.0.war /JetspeedTraining/tomcat-express/webapps/express-demo.war
+
+# Windows
+cd \JetspeedTraining\workspace\jetexpress\applications\express-demo
+copy target\express-demo-1.0.war \JetspeedTraining\tomcat-express\webapps\express-demo.war
+
+     ]]>
+	</source> 
+	<p>This will deploy your portlet application. Next, lets see how to add your new portlets to a page.
+	</p>      
+	  <p>
+	    <a href='portlet-app.html'>Previous</a> <a href='pages.html'>Next</a>
+	  </p>            
+    </section>
+  </body>
+</document>
+

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/build-it.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/pages.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/pages.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/pages.xml (original)
+++ portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/pages.xml Fri Dec 12 04:06:29 2008
@@ -1,78 +1,78 @@
-<?xml version="1.0"?>
-<!--
+<?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>Configuring Portal Pages</title>
-    <subtitle>Configuring Portal Pages</subtitle>
-	<authors>
-		<person name="David Sean Taylor" email="taylor@apache.org" />
-	</authors>
-  </properties>
-  <body>
-    <section name="Configuring Portal Pages">
-      <p>      
-       Now that you have generated a portlet app named <b>express-demo</b>, we are ready to integrate
-       the new portlets into our system. This is done by adding the portlets to the portal pages.
-       These pages are also known as PSML files. Your pages makeup the navigational site of your system.
-	   The new pages we are going to add will have references to the new portlets added in the express-demo
-	   portlet applications. Of course users can use the Portlet Selector and Jetspeed Customizer to
-	   select portlets interactively. Here we are setting up the collection of pages that will  always
-	   be a part of your portal. The file-system tree-like collection of pages is known as your <b>portal site</b>	   
-      </p>
-      <p>
-      We provide a quick Ant task to copy in the new, preconfigured pages:
-      </p>
-	 <source>
-	 <![CDATA[
-# Linux	 
-cd /JetspeedTraining/workspace/jetexpress/
-
-# Windows
-cd \JetspeedTraining\workspace\jetexpress\
-
-ant copy-page-resources
-     ]]>
-	</source> 
-      <p>
-      Open up some of the pages found under <i>portal/src/webapp/WEB-INF/pages/</i>.
-      You will see that we've added a new <i>Contact Us</i> page, and added the some new demo portlets
-      the the default page. We have also changed the default themes and decorators
-      for all administrative pages.
-      </p>
-      <p>
-      Go ahead and deploy those changes:
-      </p>	
-	 <source>
-	 <![CDATA[
-ant
-     ]]>
-	</source> 
-	<p>This will deploy your new pages. Refresh the portal home page to see the new portlets:
-	</p>      
-	<img src="../images/new-home.png"/>
-	<p>
-	Likewise for the desktop:
-	</p>
-	<img src="../images/new-home2.png"/>	
-	  <p>	  
-	    <a href='portlet-app.html'>Previous</a> <a href='../04/overview.html'>Next</a>
-	  </p>            
-    </section>
-  </body>
-</document>
-
+  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>Configuring Portal Pages</title>
+    <subtitle>Configuring Portal Pages</subtitle>
+	<authors>
+		<person name="David Sean Taylor" email="taylor@apache.org" />
+	</authors>
+  </properties>
+  <body>
+    <section name="Configuring Portal Pages">
+      <p>      
+       Now that you have generated a portlet app named <b>express-demo</b>, we are ready to integrate
+       the new portlets into our system. This is done by adding the portlets to the portal pages.
+       These pages are also known as PSML files. Your pages makeup the navigational site of your system.
+	   The new pages we are going to add will have references to the new portlets added in the express-demo
+	   portlet applications. Of course users can use the Portlet Selector and Jetspeed Customizer to
+	   select portlets interactively. Here we are setting up the collection of pages that will  always
+	   be a part of your portal. The file-system tree-like collection of pages is known as your <b>portal site</b>	   
+      </p>
+      <p>
+      We provide a quick Ant task to copy in the new, preconfigured pages:
+      </p>
+	 <source>
+	 <![CDATA[
+# Linux	 
+cd /JetspeedTraining/workspace/jetexpress/
+
+# Windows
+cd \JetspeedTraining\workspace\jetexpress\
+
+ant copy-page-resources
+     ]]>
+	</source> 
+      <p>
+      Open up some of the pages found under <i>portal/src/webapp/WEB-INF/pages/</i>.
+      You will see that we've added a new <i>Contact Us</i> page, and added the some new demo portlets
+      the the default page. We have also changed the default themes and decorators
+      for all administrative pages.
+      </p>
+      <p>
+      Go ahead and deploy those changes:
+      </p>	
+	 <source>
+	 <![CDATA[
+ant
+     ]]>
+	</source> 
+	<p>This will deploy your new pages. Refresh the portal home page to see the new portlets:
+	</p>      
+	<img src="../images/new-home.png"/>
+	<p>
+	Likewise for the desktop:
+	</p>
+	<img src="../images/new-home2.png"/>	
+	  <p>	  
+	    <a href='portlet-app.html'>Previous</a> <a href='../04/overview.html'>Next</a>
+	  </p>            
+    </section>
+  </body>
+</document>
+

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/pages.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/03/portlet-app.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/eclipse.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/eclipse.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/eclipse.xml (original)
+++ portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/eclipse.xml Fri Dec 12 04:06:29 2008
@@ -1,92 +1,92 @@
-<?xml version="1.0"?>
-<!--
+<?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>Eclipse Integration</title>
-		<subtitle>Eclipse Integration</subtitle>
-		<authors>
-			<person name="David Sean Taylor" email="taylor@apache.org" />
-		</authors>
-	</properties>
-	<body>
-    <section name="Eclipse Integration">
-      <p> 
-      Before getting started, lets get Eclipse setup.
-      Lets create a Eclipse project for the jetexpress project.
-      Maven-2 can create Eclipse project and classpath files from your Maven-2 project POM,
-      automatically bringing in all dependencies:
-      </p>
-	 <source>
-	 <![CDATA[
-# Linux	 
-cd /JetspeedTraining/workspace/jetexpress
-mvn eclipse:eclipse
-cp portal/.classpath .
-cp portal/.project .
-# Windows
-cd \JetspeedTraining\workspace\jetexpress
-mvn eclipse:eclipse
-copy portal\.classpath .
-copy portal\.project .
-     ]]>
-     </source>	  	        
-      <p>	      	  
-	Lets do the same for the <i>express-demo</i> portlet application.
-	You may prefer to actually create a new Eclipse project to represent the portlet app subproject.
-	We recommend this, since Eclipse doesn't work very well multi-Maven projects. Best to break
-	them out into one Maven project == one Eclipse project:
-	</p>
-	 <source>
-	 <![CDATA[
-# Linux	 
-cd /JetspeedTraining/workspace/jetexpress/applications/express-demo
-mvn eclipse:eclipse
-# Windows
-cd \JetspeedTraining\workspace\jetexpress\applications\express-demo
-mvn eclipse:eclipse
-     ]]>
-     </source>	  	        
-	<p>
-	Now lets import these new projects. From the eclipse menu, select File->Import:
-	</p>
-	<img src="../images/import-project.png"/>	
-	<img src="../images/import-project2.png"/>		
-	<p>
-	Repeat for both the applications/express-demo project.
-	</p>
-	<p>
-	Next, lets setup a classpath variable to point at the Maven Repo, effectively resolving the jars for Eclipse.
-	In Eclipse, go to Window->Preferences->Java->Build Path->Classpath Variables->New...:
-	</p>
-	<img src="../images/eclipse-classpath.png"/>	
-	  <p>
-	If you would like to work with the Jetspeed source from the SVN Trunk, you will need to install the Subversion Plugin for Eclipse.
-	After doing so, simply check out the project using the Subversion plugin:
-	  </p>	
-	<img src="../images/svn1.png"/>	
-	<img src="../images/svn2.png"/>			  
-	<img src="../images/svn3.png"/>			  	
-	  <p>
-	We are now ready to start developing with Eclipse. 
-	  </p>
-	  <p>	  
-	    <a href='overview.html'>Previous</a> <a href='hello.html'>Next</a>
-	  </p>            	   
-	  </section>
-	</body>
+	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>Eclipse Integration</title>
+		<subtitle>Eclipse Integration</subtitle>
+		<authors>
+			<person name="David Sean Taylor" email="taylor@apache.org" />
+		</authors>
+	</properties>
+	<body>
+    <section name="Eclipse Integration">
+      <p> 
+      Before getting started, lets get Eclipse setup.
+      Lets create a Eclipse project for the jetexpress project.
+      Maven-2 can create Eclipse project and classpath files from your Maven-2 project POM,
+      automatically bringing in all dependencies:
+      </p>
+	 <source>
+	 <![CDATA[
+# Linux	 
+cd /JetspeedTraining/workspace/jetexpress
+mvn eclipse:eclipse
+cp portal/.classpath .
+cp portal/.project .
+# Windows
+cd \JetspeedTraining\workspace\jetexpress
+mvn eclipse:eclipse
+copy portal\.classpath .
+copy portal\.project .
+     ]]>
+     </source>	  	        
+      <p>	      	  
+	Lets do the same for the <i>express-demo</i> portlet application.
+	You may prefer to actually create a new Eclipse project to represent the portlet app subproject.
+	We recommend this, since Eclipse doesn't work very well multi-Maven projects. Best to break
+	them out into one Maven project == one Eclipse project:
+	</p>
+	 <source>
+	 <![CDATA[
+# Linux	 
+cd /JetspeedTraining/workspace/jetexpress/applications/express-demo
+mvn eclipse:eclipse
+# Windows
+cd \JetspeedTraining\workspace\jetexpress\applications\express-demo
+mvn eclipse:eclipse
+     ]]>
+     </source>	  	        
+	<p>
+	Now lets import these new projects. From the eclipse menu, select File->Import:
+	</p>
+	<img src="../images/import-project.png"/>	
+	<img src="../images/import-project2.png"/>		
+	<p>
+	Repeat for both the applications/express-demo project.
+	</p>
+	<p>
+	Next, lets setup a classpath variable to point at the Maven Repo, effectively resolving the jars for Eclipse.
+	In Eclipse, go to Window->Preferences->Java->Build Path->Classpath Variables->New...:
+	</p>
+	<img src="../images/eclipse-classpath.png"/>	
+	  <p>
+	If you would like to work with the Jetspeed source from the SVN Trunk, you will need to install the Subversion Plugin for Eclipse.
+	After doing so, simply check out the project using the Subversion plugin:
+	  </p>	
+	<img src="../images/svn1.png"/>	
+	<img src="../images/svn2.png"/>			  
+	<img src="../images/svn3.png"/>			  	
+	  <p>
+	We are now ready to start developing with Eclipse. 
+	  </p>
+	  <p>	  
+	    <a href='overview.html'>Previous</a> <a href='hello.html'>Next</a>
+	  </p>            	   
+	  </section>
+	</body>
 </document>
\ No newline at end of file

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/eclipse.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/hello.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/hello.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/hello.xml (original)
+++ portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/hello.xml Fri Dec 12 04:06:29 2008
@@ -1,90 +1,90 @@
-<?xml version="1.0"?>
-<!--
+<?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>Hello World</title>
-    <subtitle>Hello World Portlet</subtitle>
-	<authors>
-		<person name="David Sean Taylor" email="taylor@apache.org" />
-	</authors>
-  </properties>
-  <body>
-    <section name="Hello World Portlet">
-    <p>      
-    We are going to create a portlet using the Eclipse Java perspective.    
-    Go to the <i>express-demo</i> project, click on the <i>com.bluesunrise.portal.portlets.tutorial</i> package, and create a new Java class:
-	</p>      
-	<img src="../images/new-portlet.png"/>
-	<p>
-	You will see a new portlet in Eclipse named BonjourWorld.
-	Go ahead Override and Implement the following methods:	
-	</p>
-	<img src="../images/override-impl.png"/>
-	<p>
-	Each one of these methods is associated with a portlet mode.
-	Lets make these methods actually do something.
-	Since we are in the render phase when doView/doEdit/doHelp are called,
-	its probably best to render something. The RenderResponse 
-	renders content to the output stream of the portlet. 
-	Set the content type on the response, and then print
-	a <i>hello world</i> message using a Java Writer:	
-	</p>	
-	 <source>	
-	 <![CDATA[
-    protected void doView(RenderRequest request, RenderResponse response) throws PortletException, IOException
-    {
-        response.setContentType("text/html"); 
-        response.getWriter().println("<b>Bonjour: View Mode</b>");
-    }
-	     ]]>
-	</source> 	
-	<p>
-	Repeat the same process for Edit and Help modes.
-	Now lets edit the portlet.xml, and create a portlet descriptor entry 
-	for our portlet. Notice that the &lt;supports&gt; element contains
-	that same portlet modes that we support in our <i>do</i> methods.
-	</p>
-	 <source>	
-	 <![CDATA[
-    <portlet>
-        <description>Bonjour Monde Portlet</description>		
-        <portlet-name>BonjourMonde</portlet-name>	
-        <display-name>Bonjour Monde</display-name>
-        <portlet-class>com.bluesunrise.portal.portlets.tutorial.BonjourWorld</portlet-class>	        
-        <supports>
-            <mime-type>text/html</mime-type>
-            <portlet-mode>VIEW</portlet-mode>
-            <portlet-mode>EDIT</portlet-mode>
-            <portlet-mode>HELP</portlet-mode>            
-        </supports>
-        <supported-locale>en</supported-locale>      	
-	    <portlet-info>
-        <title>Bonjour Monde</title>
-          <short-title>Bonjour</short-title>
-          <keywords>tutorial,bonjour,hello</keywords>
-       </portlet-info>
-	</portlet>	 
-	     ]]>
-	</source> 		
-	  <p>
-	    <a href='overview.html'>Previous</a> <a href='tutorial-psml.html'>Next</a>
-	  </p>            
-    </section>
-  </body>
-</document>
-
+  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>Hello World</title>
+    <subtitle>Hello World Portlet</subtitle>
+	<authors>
+		<person name="David Sean Taylor" email="taylor@apache.org" />
+	</authors>
+  </properties>
+  <body>
+    <section name="Hello World Portlet">
+    <p>      
+    We are going to create a portlet using the Eclipse Java perspective.    
+    Go to the <i>express-demo</i> project, click on the <i>com.bluesunrise.portal.portlets.tutorial</i> package, and create a new Java class:
+	</p>      
+	<img src="../images/new-portlet.png"/>
+	<p>
+	You will see a new portlet in Eclipse named BonjourWorld.
+	Go ahead Override and Implement the following methods:	
+	</p>
+	<img src="../images/override-impl.png"/>
+	<p>
+	Each one of these methods is associated with a portlet mode.
+	Lets make these methods actually do something.
+	Since we are in the render phase when doView/doEdit/doHelp are called,
+	its probably best to render something. The RenderResponse 
+	renders content to the output stream of the portlet. 
+	Set the content type on the response, and then print
+	a <i>hello world</i> message using a Java Writer:	
+	</p>	
+	 <source>	
+	 <![CDATA[
+    protected void doView(RenderRequest request, RenderResponse response) throws PortletException, IOException
+    {
+        response.setContentType("text/html"); 
+        response.getWriter().println("<b>Bonjour: View Mode</b>");
+    }
+	     ]]>
+	</source> 	
+	<p>
+	Repeat the same process for Edit and Help modes.
+	Now lets edit the portlet.xml, and create a portlet descriptor entry 
+	for our portlet. Notice that the &lt;supports&gt; element contains
+	that same portlet modes that we support in our <i>do</i> methods.
+	</p>
+	 <source>	
+	 <![CDATA[
+    <portlet>
+        <description>Bonjour Monde Portlet</description>		
+        <portlet-name>BonjourMonde</portlet-name>	
+        <display-name>Bonjour Monde</display-name>
+        <portlet-class>com.bluesunrise.portal.portlets.tutorial.BonjourWorld</portlet-class>	        
+        <supports>
+            <mime-type>text/html</mime-type>
+            <portlet-mode>VIEW</portlet-mode>
+            <portlet-mode>EDIT</portlet-mode>
+            <portlet-mode>HELP</portlet-mode>            
+        </supports>
+        <supported-locale>en</supported-locale>      	
+	    <portlet-info>
+        <title>Bonjour Monde</title>
+          <short-title>Bonjour</short-title>
+          <keywords>tutorial,bonjour,hello</keywords>
+       </portlet-info>
+	</portlet>	 
+	     ]]>
+	</source> 		
+	  <p>
+	    <a href='overview.html'>Previous</a> <a href='tutorial-psml.html'>Next</a>
+	  </p>            
+    </section>
+  </body>
+</document>
+

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/hello.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/overview.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/overview.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/overview.xml (original)
+++ portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/overview.xml Fri Dec 12 04:06:29 2008
@@ -1,45 +1,45 @@
-<?xml version="1.0"?>
-<!--
+<?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>Portlet 101</title>
-		<subtitle>Portlet Development 101</subtitle>
-		<authors>
-			<person name="David Sean Taylor" email="taylor@apache.org" />
-		</authors>
-	</properties>
-	<body>
-    <section name="Portlet Development with the Portlet API">
-      <p> 
-        This section of the tutorial covers Portlet Development with the Java Portlet API.
-      </p>	
-      <p> 
-	   <ul>
-	     <li>Getting started with Eclipse</li>
-	     <li>Bonjour Monde Portlet: the staple Hello World demo to get things rolling introduces the portlet.xml, as well as basic Portlet API concepts.</li>
-	     <li>The Weather Portlet: using init parameters, preferences, and request parameters</li>	 
-	     <li>The Stock Quote Portlet: actions, JSP, Portlet API Tag Library</li>	 
-	     <li>Interportlet communication, more advanced Portlet programming.</li>
-	   </ul>	   
-      </p>	
-	  <p>
-	    <a href='../03/pages.html'>Previous</a> <a href='eclipse.html'>Next</a>
-	  </p>            	   
-	  </section>
-	</body>
+	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>Portlet 101</title>
+		<subtitle>Portlet Development 101</subtitle>
+		<authors>
+			<person name="David Sean Taylor" email="taylor@apache.org" />
+		</authors>
+	</properties>
+	<body>
+    <section name="Portlet Development with the Portlet API">
+      <p> 
+        This section of the tutorial covers Portlet Development with the Java Portlet API.
+      </p>	
+      <p> 
+	   <ul>
+	     <li>Getting started with Eclipse</li>
+	     <li>Bonjour Monde Portlet: the staple Hello World demo to get things rolling introduces the portlet.xml, as well as basic Portlet API concepts.</li>
+	     <li>The Weather Portlet: using init parameters, preferences, and request parameters</li>	 
+	     <li>The Stock Quote Portlet: actions, JSP, Portlet API Tag Library</li>	 
+	     <li>Interportlet communication, more advanced Portlet programming.</li>
+	   </ul>	   
+      </p>	
+	  <p>
+	    <a href='../03/pages.html'>Previous</a> <a href='eclipse.html'>Next</a>
+	  </p>            	   
+	  </section>
+	</body>
 </document>
\ No newline at end of file

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/overview.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/taglib.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/taglib.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/taglib.xml (original)
+++ portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/taglib.xml Fri Dec 12 04:06:29 2008
@@ -1,171 +1,171 @@
-<?xml version="1.0"?>
-<!--
+<?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>Taglibs</title>
-    <subtitle>Portlet API Taglib</subtitle>
-	<authors>
-		<person name="David Sean Taylor" email="taylor@apache.org" />
-	</authors>
-  </properties>
-  <body>
-    <section name="JSP and Portlet API Taglib">
-    <p>      
-    Lets create another portlet. This portlet will not have a Java class.
-    Instead it will be written entirely in JSP.
-    Note that you can mix JSP and a Java class for the implementation of your
-    Java class as you will see in the Stock Quote portlet example.
-    Go to the <i>express-demo</i> project, click on the <i>src/webapp/WEB-INF/view/</i> directory, and create a JSP 
-    file named <b>tutorial.jsp</b>. Enter the following JSP code:
-	</p>      
-	 <source>	
-	 <![CDATA[
-<%@ page session="true" contentType="text/html;charset=utf-8"%>
-<%@ taglib uri='/WEB-INF/portlet.tld' prefix='portlet'%>
-<%@ taglib uri="http://java.sun.com/jstl/core" prefix='c' %> 
-
-<portlet:defineObjects/>
-
-<portlet:renderURL var="max" windowState='maximized'/>
-<portlet:renderURL var="normal" windowState='normal'/>
-<c:out value="${renderRequest.windowState}"/>
-<c:if test="${renderRequest.windowState == 'maximized'}">
-<a href='<%=normal%>'>Normal</a>
-</c:if>
-<c:if test="${renderRequest.windowState == 'normal'}">
-<a href='<%=max%>'>Max</a>
-</c:if>
-	     ]]>
-	</source> 	
-	<p>
-	Every portlet JSP page is required to have the <b>defineObjects</b> tag 
-	at the top. Of course you also need the TLD reference.
-	Portlets need to write their links to go back to the portal, not 
-	back to each individual servlet or JSP. That is the main difference 
-	between writing portlets and servlets. If you are using a framework like
-	Struts or JSF correctly, these details should be hidden from you in 
-	the framework. The tag that we are using here is the <b>&lt;portlet:renderURL&gt;</b>.
-	It allows you to create a render phase link back to this portlet, going 
-	through the portal. You can set window states, request parameters, and
-	portlet mode changes on the URL. The other kind of link that you can create
-	is an action URL: <b>&lt;portlet:actionURL&gt;</b>, which is usually
-	used with a HTML form to post back parameters to the portlet and initial
-	a blocking action phase event for the targeted portlet.    	
-	The <b>&lt;portlet:defineObjects&gt;</b> tag declares three variables for your
-	page:
-	<table>
-	<tr>
-	<th>JSP variable</th>
-	<th>Description</th>
-	</tr>
-	<tr>
-	<td>renderRequest</td>
-	<td>The RenderRequest object</td>
-	</tr>
-	<tr>
-	<td>renderResponse</td>
-	<td>The RenderResponse object</td>
-	</tr>
-	<tr>
-	<td>portletConfig</td>
-	<td>The PortletConfig object</td>
-	</tr>
-	</table>
-	</p>	
-	<p>
-	Here is the portlet.xml for our JSP portlet.
-	It is based on the <b>GenericServletPortlet</b>, provided by Portals Bridges
-	in a jar file dependency.
-	Notice the init-param named <b>ViewPage</b>.
-	This param defines which webapp-relative JSP to use for View Mode.
-	Similiarly we have are <b>EditPage</b> for edit mode, and <b>HelpPage</b>
-	for help mode.
-	</p>
-	 <source>	
-	 <![CDATA[
- <portlet>   
-    <description>The 2nd Tutorial with JSP</description>		
-    <portlet-name>TutorialPortlet2</portlet-name>	
-    <display-name>Tutorial Portlet 2</display-name>
-    <portlet-class>org.apache.portals.bridges.common.GenericServletPortlet</portlet-class>	        
-    <init-param>
-        <name>ViewPage</name>
-        <value>/WEB-INF/view/tutorial.jsp</value>
-    </init-param>          
-    <init-param>
-        <name>EditPage</name>
-        <value>/WEB-INF/view/tutorial.jsp</value>
-    </init-param>          
-    <init-param>
-        <name>HelpPage</name>
-        <value>/WEB-INF/view/tutorial.jsp</value>
-    </init-param>              
-    <supports>
-        <mime-type>text/html</mime-type>
-        <portlet-mode>VIEW</portlet-mode>
-        <portlet-mode>EDIT</portlet-mode>        
-        <portlet-mode>HELP</portlet-mode>                
-    </supports>
-    <supported-locale>en</supported-locale>      	
-	<portlet-info>
-        <title>Tutorial Portlet</title>
-        <short-title>tutorial</short-title>
-		<keywords>tutorial,hello,JSP,taglib</keywords>
-    </portlet-info>
-    <portlet-preferences>
-        <preference>                            
-            <name>test</name>                    
-            <value>hello</value>    
-        </preference>         
-    </portlet-preferences>                      		
-</portlet> 	 
-	     ]]>
-	</source> 
-	<p>Add this portlet window fragment to the tutorial default page, underneath the BonjourMonde fragment:
-	</p>
-	 <source>
-	 <![CDATA[
-	  <fragment id="express-102" type="portlet" name="express-demo::TutorialPortlet2"/>
-     ]]>
-	</source> 				
-	<p>And then deploy your changes:
-	</p>
-	 <source>
-	 <![CDATA[
-# Linux	 
-cd /JetspeedTraining/workspace/jetexpress/
-ant
-cd applications/express-demo
-mvn 
-cp target/express-demo-1.0.war /JetspeedTraining/tomcat-express/webapps/express-demo.war
-
-# Windows
-cd \JetspeedTraining\workspace\jetexpress
-ant
-cd applications\express-demo
-mvn 
-copy target\express-demo-1.0.war \JetspeedTraining\tomcat-express\webapps\express-demo.war
-     ]]>
-	</source> 			
-	  <p>
-	    <a href='hello.html'>Previous</a> <a href='../05/jetspeed-service.html'>Next</a>
-	  </p>            
-    </section>
-  </body>
-</document>
-
+  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>Taglibs</title>
+    <subtitle>Portlet API Taglib</subtitle>
+	<authors>
+		<person name="David Sean Taylor" email="taylor@apache.org" />
+	</authors>
+  </properties>
+  <body>
+    <section name="JSP and Portlet API Taglib">
+    <p>      
+    Lets create another portlet. This portlet will not have a Java class.
+    Instead it will be written entirely in JSP.
+    Note that you can mix JSP and a Java class for the implementation of your
+    Java class as you will see in the Stock Quote portlet example.
+    Go to the <i>express-demo</i> project, click on the <i>src/webapp/WEB-INF/view/</i> directory, and create a JSP 
+    file named <b>tutorial.jsp</b>. Enter the following JSP code:
+	</p>      
+	 <source>	
+	 <![CDATA[
+<%@ page session="true" contentType="text/html;charset=utf-8"%>
+<%@ taglib uri='/WEB-INF/portlet.tld' prefix='portlet'%>
+<%@ taglib uri="http://java.sun.com/jstl/core" prefix='c' %> 
+
+<portlet:defineObjects/>
+
+<portlet:renderURL var="max" windowState='maximized'/>
+<portlet:renderURL var="normal" windowState='normal'/>
+<c:out value="${renderRequest.windowState}"/>
+<c:if test="${renderRequest.windowState == 'maximized'}">
+<a href='<%=normal%>'>Normal</a>
+</c:if>
+<c:if test="${renderRequest.windowState == 'normal'}">
+<a href='<%=max%>'>Max</a>
+</c:if>
+	     ]]>
+	</source> 	
+	<p>
+	Every portlet JSP page is required to have the <b>defineObjects</b> tag 
+	at the top. Of course you also need the TLD reference.
+	Portlets need to write their links to go back to the portal, not 
+	back to each individual servlet or JSP. That is the main difference 
+	between writing portlets and servlets. If you are using a framework like
+	Struts or JSF correctly, these details should be hidden from you in 
+	the framework. The tag that we are using here is the <b>&lt;portlet:renderURL&gt;</b>.
+	It allows you to create a render phase link back to this portlet, going 
+	through the portal. You can set window states, request parameters, and
+	portlet mode changes on the URL. The other kind of link that you can create
+	is an action URL: <b>&lt;portlet:actionURL&gt;</b>, which is usually
+	used with a HTML form to post back parameters to the portlet and initial
+	a blocking action phase event for the targeted portlet.    	
+	The <b>&lt;portlet:defineObjects&gt;</b> tag declares three variables for your
+	page:
+	<table>
+	<tr>
+	<th>JSP variable</th>
+	<th>Description</th>
+	</tr>
+	<tr>
+	<td>renderRequest</td>
+	<td>The RenderRequest object</td>
+	</tr>
+	<tr>
+	<td>renderResponse</td>
+	<td>The RenderResponse object</td>
+	</tr>
+	<tr>
+	<td>portletConfig</td>
+	<td>The PortletConfig object</td>
+	</tr>
+	</table>
+	</p>	
+	<p>
+	Here is the portlet.xml for our JSP portlet.
+	It is based on the <b>GenericServletPortlet</b>, provided by Portals Bridges
+	in a jar file dependency.
+	Notice the init-param named <b>ViewPage</b>.
+	This param defines which webapp-relative JSP to use for View Mode.
+	Similiarly we have are <b>EditPage</b> for edit mode, and <b>HelpPage</b>
+	for help mode.
+	</p>
+	 <source>	
+	 <![CDATA[
+ <portlet>   
+    <description>The 2nd Tutorial with JSP</description>		
+    <portlet-name>TutorialPortlet2</portlet-name>	
+    <display-name>Tutorial Portlet 2</display-name>
+    <portlet-class>org.apache.portals.bridges.common.GenericServletPortlet</portlet-class>	        
+    <init-param>
+        <name>ViewPage</name>
+        <value>/WEB-INF/view/tutorial.jsp</value>
+    </init-param>          
+    <init-param>
+        <name>EditPage</name>
+        <value>/WEB-INF/view/tutorial.jsp</value>
+    </init-param>          
+    <init-param>
+        <name>HelpPage</name>
+        <value>/WEB-INF/view/tutorial.jsp</value>
+    </init-param>              
+    <supports>
+        <mime-type>text/html</mime-type>
+        <portlet-mode>VIEW</portlet-mode>
+        <portlet-mode>EDIT</portlet-mode>        
+        <portlet-mode>HELP</portlet-mode>                
+    </supports>
+    <supported-locale>en</supported-locale>      	
+	<portlet-info>
+        <title>Tutorial Portlet</title>
+        <short-title>tutorial</short-title>
+		<keywords>tutorial,hello,JSP,taglib</keywords>
+    </portlet-info>
+    <portlet-preferences>
+        <preference>                            
+            <name>test</name>                    
+            <value>hello</value>    
+        </preference>         
+    </portlet-preferences>                      		
+</portlet> 	 
+	     ]]>
+	</source> 
+	<p>Add this portlet window fragment to the tutorial default page, underneath the BonjourMonde fragment:
+	</p>
+	 <source>
+	 <![CDATA[
+	  <fragment id="express-102" type="portlet" name="express-demo::TutorialPortlet2"/>
+     ]]>
+	</source> 				
+	<p>And then deploy your changes:
+	</p>
+	 <source>
+	 <![CDATA[
+# Linux	 
+cd /JetspeedTraining/workspace/jetexpress/
+ant
+cd applications/express-demo
+mvn 
+cp target/express-demo-1.0.war /JetspeedTraining/tomcat-express/webapps/express-demo.war
+
+# Windows
+cd \JetspeedTraining\workspace\jetexpress
+ant
+cd applications\express-demo
+mvn 
+copy target\express-demo-1.0.war \JetspeedTraining\tomcat-express\webapps\express-demo.war
+     ]]>
+	</source> 			
+	  <p>
+	    <a href='hello.html'>Previous</a> <a href='../05/jetspeed-service.html'>Next</a>
+	  </p>            
+    </section>
+  </body>
+</document>
+

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/taglib.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/tutorial-psml.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/tutorial-psml.xml?rev=725977&r1=725976&r2=725977&view=diff
==============================================================================
--- portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/tutorial-psml.xml (original)
+++ portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/tutorial-psml.xml Fri Dec 12 04:06:29 2008
@@ -1,90 +1,90 @@
-<?xml version="1.0"?>
-<!--
+<?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>Adding a Page for the Tutorial Portlets</title>
-    <subtitle>Adding a Page for the Tutorial Portlets</subtitle>
-	<authors>
-		<person name="David Sean Taylor" email="taylor@apache.org" />
-	</authors>
-  </properties>
-  <body>
-    <section name="Adding a Page for the Tutorial Portlets">
-	<p>
-	Now that we've created a new portlet, lets add a page to hold that portlet.
-	In the <b>jetexpress</b> project, lets add a folder to the root of our site named
+  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>Adding a Page for the Tutorial Portlets</title>
+    <subtitle>Adding a Page for the Tutorial Portlets</subtitle>
+	<authors>
+		<person name="David Sean Taylor" email="taylor@apache.org" />
+	</authors>
+  </properties>
+  <body>
+    <section name="Adding a Page for the Tutorial Portlets">
+	<p>
+	Now that we've created a new portlet, lets add a page to hold that portlet.
+	In the <b>jetexpress</b> project, lets add a folder to the root of our site named
 	<i>portal/src/webapp/WEB-INF/pages/tutorial/</i>. In addition to creating the folder,
-	you will need to create a <i>folder.metadata</i> file:
-	</p>
-	 <source>	
-	 <![CDATA[	
-<?xml version="1.0" encoding="UTF-8"?>
-<folder>
-  <title >Tutorial</title>  
-  <metadata name="title" xml:lang="fr">Autodidacte</metadata>
-
-  <security-constraints>
-    <security-constraints-ref>public-edit</security-constraints-ref>
-  </security-constraints>
-</folder>	 
-	     ]]>
-	</source> 		
-	<p>
-	Then lets add a new page named <b>default-page.psml</b> under the tutorial directory.
-	Add a portlet window to reference our new portlet:
-	</p>
-	 <source>	
-	 <![CDATA[
-<page>
-  <defaults layout-decorator="express-page" 
-            portlet-decorator="express-portlet"
-            skin="express"/>
-  <title>JetExpress Tutorials</title>
-  <short-title>Tutorials</short-title>
-  <fragment id="tutorial-100" type="layout" name="jetspeed-layouts::VelocityTwoColumns">  
-	  <fragment id="express-101" type="portlet" name="express-demo::BonjourMonde"/>
-  </fragment>
-</page>	 
-	     ]]>
-	</source> 	
-	<p>Lets deploy our portlet and the new pages:
-	</p>
-	 <source>	
-	 <![CDATA[
-# Linux	 
-cd /JetspeedTraining/workspace/jetexpress
-ant
-cd applications/express-demo
-mvn 
-cp target/express-demo-1.0.war /JetspeedTraining/tomcat-express/webapps/express-demo.war
-
-# Windows
-cd \JetspeedTraining\workspace\jetexpress
-ant
-cd applications\express-demo
-mvn 
-copy target\express-demo-1.0.war \JetspeedTraining\tomcat-express\webapps\express-demo.war
-	     ]]>
-	</source> 		
-	  <p>
-	    <a href='hello.html'>Previous</a> <a href='taglib.html'>Next</a>
-	  </p>            	
-    </section>
-  </body>
-</document>
+	you will need to create a <i>folder.metadata</i> file:
+	</p>
+	 <source>	
+	 <![CDATA[	
+<?xml version="1.0" encoding="UTF-8"?>
+<folder>
+  <title >Tutorial</title>  
+  <metadata name="title" xml:lang="fr">Autodidacte</metadata>
+
+  <security-constraints>
+    <security-constraints-ref>public-edit</security-constraints-ref>
+  </security-constraints>
+</folder>	 
+	     ]]>
+	</source> 		
+	<p>
+	Then lets add a new page named <b>default-page.psml</b> under the tutorial directory.
+	Add a portlet window to reference our new portlet:
+	</p>
+	 <source>	
+	 <![CDATA[
+<page>
+  <defaults layout-decorator="express-page" 
+            portlet-decorator="express-portlet"
+            skin="express"/>
+  <title>JetExpress Tutorials</title>
+  <short-title>Tutorials</short-title>
+  <fragment id="tutorial-100" type="layout" name="jetspeed-layouts::VelocityTwoColumns">  
+	  <fragment id="express-101" type="portlet" name="express-demo::BonjourMonde"/>
+  </fragment>
+</page>	 
+	     ]]>
+	</source> 	
+	<p>Lets deploy our portlet and the new pages:
+	</p>
+	 <source>	
+	 <![CDATA[
+# Linux	 
+cd /JetspeedTraining/workspace/jetexpress
+ant
+cd applications/express-demo
+mvn 
+cp target/express-demo-1.0.war /JetspeedTraining/tomcat-express/webapps/express-demo.war
+
+# Windows
+cd \JetspeedTraining\workspace\jetexpress
+ant
+cd applications\express-demo
+mvn 
+copy target\express-demo-1.0.war \JetspeedTraining\tomcat-express\webapps\express-demo.war
+	     ]]>
+	</source> 		
+	  <p>
+	    <a href='hello.html'>Previous</a> <a href='taglib.html'>Next</a>
+	  </p>            	
+    </section>
+  </body>
+</document>
 	
\ No newline at end of file

Propchange: portals/jetspeed-2/portal/trunk/tutorial/xdocs/04/tutorial-psml.xml
------------------------------------------------------------------------------
    svn:eol-style = native



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message