Title: [waffle-scm] [218] trunk/distribution/src/site/content/tutorials: Fixed rendering issues caused by skewed divs.
Revision
218
Author
mauro
Date
2007-07-03 08:45:01 -0500 (Tue, 03 Jul 2007)

Log Message

Fixed rendering issues caused by skewed divs.

Modified Paths


Diff

Modified: trunk/distribution/src/site/content/tutorials/tutorial-one.html (217 => 218)

--- trunk/distribution/src/site/content/tutorials/tutorial-one.html	2007-07-03 13:40:38 UTC (rev 217)
+++ trunk/distribution/src/site/content/tutorials/tutorial-one.html	2007-07-03 13:45:01 UTC (rev 218)
@@ -41,7 +41,7 @@
         this.model = model;
     }
 }</pre></div>
-</div>
+
 <h3>Registrar</h3>
 <p>As stated earlier, a Controller is not active in Waffle until it
 has been registered with the Registrar. So now we will create a simple
@@ -62,7 +62,7 @@
         register(&quot;automobile&quot;, Automobile.class);
     }
 }</pre></div>
-</div>
+
 <h3>web.xml</h3>
 <p>While Waffle does not require any proprietary XML configuration
 files we still must create a <b>web.xml</b>. The web.xml example below
@@ -128,7 +128,7 @@
 &lt;/web-app&gt;</pre></div>
   </li>
 </ol>
-</div>
+
 <h3>View</h3>
 <p>We will create a very simple view to display the content of the
 Controller. The following example uses a JSP and simply displays the
@@ -156,9 +156,9 @@
     &lt;input type=&quot;submit&quot;/&gt;
 &lt;/form&gt;
 &lt;/html&gt;</pre></div>
-</div>
-</div>
-<h3>Application structure (WAR File)</h3>
+
+
+<h3>Webapp structure (WAR file)</h3>
 <p>An application built with Waffle is similar to most other Java
 web based applications. The following provides an overview of how you
 might layout the code for this tutorial:</p>
@@ -183,7 +183,7 @@
   </a> you'll need to include the jar files that each of those projects may
   require.</dd>
 </dl>
-</div>
+
 <h3>Running the application</h3>
 <p>Now the application can be deployed to a Servlet container (e.g.,
 Tomcat, Jetty). So when we run the application and direct the browser to
@@ -198,13 +198,13 @@
 to the original url we will now have: <b>http://localhost:8080/hello/automobile.waffle?model=ranger</b>.
 Notice that the url and the value of the Model field has been updated.</p>
 <img src="" />
-</div>
+
 <h3>More to see</h3>
 <p>This has only been an introduction to Waffle and it provides a
 good starting point to understanding how it works. Continue on to <a
   href="" Part two</a> to see how <b>ControllerMethods</b>
 can be dynamically invoked on Controllers.</p>
-</div>
+
 </body>
 
 </html>

Modified: trunk/distribution/src/site/content/tutorials/tutorial-two.html (217 => 218)

--- trunk/distribution/src/site/content/tutorials/tutorial-two.html	2007-07-03 13:40:38 UTC (rev 217)
+++ trunk/distribution/src/site/content/tutorials/tutorial-two.html	2007-07-03 13:45:01 UTC (rev 218)
@@ -206,7 +206,7 @@
     </tr>
   </tbody>
 </table>
-</div>
+
 <h4>ActionMethod return types</h4>
 <p>Waffle will react differently depending on what is returned, or
 thrown, from an <b>ActionMethod</b> after it has been invoked. Below we
@@ -235,7 +235,7 @@
   type of requests. Imagine these type of ActionMethod returning HTML or
   JSON messages directly.</li>
 </ul>
-</div>
+
 <h4>Caveat: Ambiguous methods</h4>
 <p>Waffle determines which ActionMethod to invoke by examining the
 Controller with reflection. If your Controller contains an overloaded
@@ -254,8 +254,7 @@
 Object)</b>, without incident. Why? Because the String value &quot;bar&quot;
 is not assignable (and cannot be automatically converted) to the <i>Map</i>
 class, so no ambiguity will exist.</p>
-</div>
-</div>
+
 </body>
 
 </html>


To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Reply via email to