svn commit: r377307 - /struts/shale/trunk/xdocs/features-reusable-views.xml

[ws...@apache.org]

Author: wsmoak
Date: Sun Feb 12 21:48:15 2006
New Revision: 377307

URL: http://svn.apache.org/viewcvs?rev=377307&view=rev
Log:
Added links to Tapestry and Tiles, and fixed a duplicate anchor.

Modified:
    struts/shale/trunk/xdocs/features-reusable-views.xml

Modified: struts/shale/trunk/xdocs/features-reusable-views.xml
URL: http://svn.apache.org/viewcvs/struts/shale/trunk/xdocs/features-reusable-views.xml?rev=377307&r1=377306&r2=377307&view=diff
==============================================================================
--- struts/shale/trunk/xdocs/features-reusable-views.xml (original)
+++ struts/shale/trunk/xdocs/features-reusable-views.xml Sun Feb 12 21:48:15 2006
@@ -24,7 +24,7 @@
 		  <ul>
 		    <li><i>HTML Views</i></li>
 			 <p> 
-			 Similar to <a href="">Tapestry</a> and 
+			 Similar to <a href="http://jakarta.apache.org/tapestry/">Tapestry</a> and 
 			 <a href="https://facelets.dev.java.net">Facelets</a>, you define your
 			 views in HTML. For dynamic content, you tie HTML elements to JSF components
 			 with a <code>jsfid</code> attribute--when Clay renders your view, it
@@ -39,7 +39,7 @@
 			 <p>
 			 You can define a component as an extension of an existing component and 
 			 then override or add attributes. This mechamism is similar to the inheritance
-			 mechanism built into the popular <a href="">Tiles</a> framework for composing
+			 mechanism built into the popular <a href="http://struts.apache.org/struts-tiles">Tiles</a> framework for composing
 			 web pages from discrete JSP fragments, known as tiles. In fact, Clay's features
 			 are sophisticated enough that Clay can give you much of the same benefits that
 			 Tiles users enjoy.
@@ -60,7 +60,7 @@
 		  see the Shale javadoc.<i>  Todo: add sections on composition and symbols</i></p>
       </subsection>
 
-      <a name="clay-view-options"/>
+      <a name="clay-html-views"/>
       <subsection name="HTML Views">
 		  <p>Back in the early days of J2EE, when people wrote applications that
 		  were mostly collections of servlets, everybody implemented their views in HTML.
@@ -81,7 +81,8 @@
 		  <p>If you'd like your graphic designers to implement your look and feel while your
 		  software developers work on components, then JSP is a terrible solution. I can see
 		  those of you in the back of the room nodding your heads, so I won't preach to the choir.
-		  The Apache <a href="">Tapestry</a> framework was the first Java web framework that not 
+		  The Apache <a href="http://jakarta.apache.org/tapestry/">Tapestry</a> 
+        framework was the first Java web framework that not 
 		  only acknowledged that fact, but, more importantly, did something about it.</p>
 
 		  <p>Tapestry maintains a strict separation between graphic designers and software
@@ -104,7 +105,7 @@
         <p><img src="images/login.jpg" alt="Shale Use Cases - Clay Login Example"/></p>
 		  <p>This application uses Tiles, so its JSP pages are pretty well carved up. We're
 		  going to look at the JSP page that implements the login form. (Don't sweat the
-		  deatils)</p>
+		  details)</p>
 <pre>
 &lt;%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %&gt;
 &lt;%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %&gt;



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