- Revision
- 502
- Author
- paul
- Date
- 2007-12-18 15:53:22 -0600 (Tue, 18 Dec 2007)
Log Message
words with mauro
Modified Paths
- trunk/waffle-distribution/src/site/content/best-practices.html
- trunk/waffle-distribution/src/site/content/index.html
- trunk/waffle.ipr
Diff
Modified: trunk/waffle-distribution/src/site/content/best-practices.html (501 => 502)
--- trunk/waffle-distribution/src/site/content/best-practices.html 2007-12-18 18:04:44 UTC (rev 501) +++ trunk/waffle-distribution/src/site/content/best-practices.html 2007-12-18 21:53:22 UTC (rev 502) @@ -1,8 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<title>Best Practices</title> -</head> +<html><head> +<title>Best Practices</title></head> + <body> <h2>Best Practices</h2> @@ -17,7 +16,6 @@ of <i>void</i>. Generally it is not a good practice to have null returned, take a look at how Exceptions are handled when produced from an <i>ActionMethod</i>. </li> - <li>More to come ...</li> + <li>More to come ....</li> </ul> -</body> -</html> +</body></html> \ No newline at end of file
Modified: trunk/waffle-distribution/src/site/content/index.html (501 => 502)
--- trunk/waffle-distribution/src/site/content/index.html 2007-12-18 18:04:44 UTC (rev 501) +++ trunk/waffle-distribution/src/site/content/index.html 2007-12-18 21:53:22 UTC (rev 502) @@ -1,10 +1,8 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html><head> +<title>Waffle</title></head> -<html> -<head> -<title>Waffle</title> -</head> <body> <h2>Waffle Web Framework</h2> @@ -16,29 +14,28 @@ <p>Waffle is different from the multitude of web frameworks that exist today, in that Waffle:</p> <ul> - <li>does <b>not</b> have any mandatory XML configuration files + <li>has no mandatory XML configuration files (beyond a minimalist web.xml required by any J2EE-compliant webapp)</li> - <li>does <b>not</b> have a proprietary UI templating language</li> - <li>does <b>not</b> have a base action class to extend or interface to implement</li> - <li>does <b>not</b> have a cumbersome setter-based injection mechanism and an execute method for controllers</li> - <li>does <b>not</b> have a steep learning curve</li> + <li>is interoperable with best-of-breed UI templating technologies</li> + <li>does not have a base controller class to extend or interface to implement</li> + <li>has controller classes that can support multiple actions, each a single method<b></b> rather than a sequence of initialiation/settter/execute methods</li><li>has a small learning curve</li> </ul> <p>Application built upon Waffle only need to be aware of three things:</p> <ol type="1"> <li><b>Controllers</b> - in Waffle <b>a - Controller is simply a plain old Java object (POJO)</b>, ie it does <b>not</b> + Controller class is simply a plain old Java object (POJO)</b>, ie it does <b>not</b> need to extend or implement any specific class or interface.</li> - <li><b>ActionMethod</b> - in Waffle <b>an ActionMethod is - simply a method defined in your Controller class</b>. Any method can be + <li><b>Action Method</b> - in Waffle <b>an Action Method is + simply a method defined in your Controller class</b> (and optionally annotated with @ActionMethod). Any method can be used regardless of its signature or return type. Waffle will react differently depending on what is returned from the ActionMethod, see <a href="" Methods</a> for further details.</li> - <li><b>Registrar</b> - the Registrar is where the <i>Controllers</i>, + <li><b>Registrar</b> - the Registrar class is where the <i>Controllers</i>, and other components your application depends on, are registered. Typically, most web frameworks require your applications to create special XML file(s) - for this, but int Waffle <b>Registrars are Java object that allow you to implement + for this, but int Waffle <b>Registrars are Java objects that allow you to implement your business logic more efficiently</b>. Of course, Waffle does allow - but <b>does not mandate</b> - a Registrar to read a configuration from a file, be it XML or a scripting language. @@ -51,7 +48,7 @@ </ul> <h3>Choices of markup language</h3> <p>As Waffle does not come with a HTML markup technology, it plays -well with other 'best practice' solutions:</p> +well with other 'best practice' and established solutions, such as:</p> <ul> <li>JSP - with or without supplied taglibs</li> <li>Freemarker</li> @@ -68,7 +65,4 @@ <div class="clear"></div> -</body> - - -</html> +</body></html> \ No newline at end of file
Modified: trunk/waffle.ipr (501 => 502)
--- trunk/waffle.ipr 2007-12-18 18:04:44 UTC (rev 501) +++ trunk/waffle.ipr 2007-12-18 21:53:22 UTC (rev 502) @@ -85,39 +85,12 @@ <autodetection-disabled> <facet-type id="web"> <modules> - <module name="waffle-migration-example"> - <files> - <file url="" /> - </files> - </module> - <module name="waffle-simple-example"> - <files> - <file url="" /> - <file url="" /> - <file url="" /> - </files> - </module> - <module name="waffle-freemarker-example"> - <files> - <file url="" /> - </files> - </module> - <module name="waffle-paranamer-example"> - <files> - <file url="" /> - <file url="" /> - </files> - </module> - <module name="waffle-jruby-example"> - <files> - <file url="" /> - </files> - </module> - <module name="waffle-mydvds-example"> - <files> - <file url="" /> - </files> - </module> + <module name="waffle-migration-example" /> + <module name="waffle-simple-example" /> + <module name="waffle-freemarker-example" /> + <module name="waffle-paranamer-example" /> + <module name="waffle-jruby-example" /> + <module name="waffle-mydvds-example" /> <module name="waffle"> <files> <file url="" /> @@ -433,8 +406,5 @@ <component name="com.intellij.profile.ui.ErrorOptionsConfigurable" proportions="" version="1"> <option name="myLastEditedConfigurable" /> </component> - <UsedPathMacros> - <macro name="M2_REPOSITORY" /> - </UsedPathMacros> </project>
To unsubscribe from this list please visit:
