- Revision
- 369
- Author
- mauro
- Date
- 2007-11-13 09:04:17 -0600 (Tue, 13 Nov 2007)
Log Message
Updated front-page description.
Modified Paths
Diff
Modified: trunk/distribution/src/site/content/index.html (368 => 369)
--- trunk/distribution/src/site/content/index.html 2007-11-13 11:54:55 UTC (rev 368) +++ trunk/distribution/src/site/content/index.html 2007-11-13 15:04:17 UTC (rev 369) @@ -13,58 +13,59 @@ enterprise level web-based business applications, but with the least possible number of source lines to achieve that.</p> -<p>Waffle is different than the multitude of web frameworks that -exist today. Waffle :</p> +<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 - beyond a minimalist web.xml required by any J2EE-compliant webapp</li> - <li>does <b>NOT</b> have a steep learning curve</li> - <li>does <b>NOT</b> have a proprietary UI templating language</li> - <li>does <strong>NOT</strong> force you to extend base classes or - implement interfaces</li> - <li>does <strong>NOT</strong> have a cumbersome series of setter - methods and an execute method for controllers</li> + <li>does <b>not</b> have any 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> </ul> <p>Application built upon Waffle only need to be aware of three things:</p> <ol type="1"> - <li><b>Controllers</b> - an controller in Waffle does <b>not</b> - need to extend or implement any specific class or interface because <b>a - controller is simply a plain old Java object (POJO)</b>.</li> + <li><b>Controllers</b> - in Waffle <b>a + Controller 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 used regardless of its signature or return type. Waffle will react - differently depending on what is returned from the ActionMethod so - take a look at this section for further details.</li> - <li><b>Registrar</b> - the Registrar is where you go to register - the <i>Controllers</i>, and other common components, your application - is dependent on. Typically most web frameworks require your - applications to create special XML file(s) for this, but <b>with - Waffle you'll spend less time playing with XML and more time building - business logic.</b></li> + 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>, + 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 + 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. + </li> </ol> <p>Additionally, Waffle provides:</p> <ul> <li>Transparent REST functionality for controllers.</li> <li>Transparent JSON functionality for controllers.</li> </ul> -<h3>Getting started</h3> -<p>The best way to get started is to look at the examples</p> -<ul> - <li><a href="" Hello World</a></li> - <li><a href="" Simple - Calculator</a></li> -</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> <ul> - <li>JSP with or without supplied taglibs</li> + <li>JSP - with or without supplied taglibs</li> <li>Freemarker</li> <li>Velocity</li> <li>Ruby's ERB</li> </ul> +<h3>Getting started</h3> +<p>The best way to get started is to look at the examples</p> +<ul> + <li><a href="" Hello World</a></li> + <li><a href="" Simple + Calculator</a></li> +</ul> + <div class="clear"></div> </body>
Modified: trunk/pom.xml (368 => 369)
--- trunk/pom.xml 2007-11-13 11:54:55 UTC (rev 368) +++ trunk/pom.xml 2007-11-13 15:04:17 UTC (rev 369) @@ -10,7 +10,8 @@ <description> Waffle is a Java action-based web framework that was built to support enterprise-level web-based business applications, without having a mandatory - XML configuration and a proprietory UI markup. Its guiding principles + XML configuration (beyond the minimal web.xml required by any webapp) + nor a proprietary UI markup language. Its guiding principles are simplicity, pluggability and interoperability. </description> <url>http://waffle.codehaus.org</url>
To unsubscribe from this list please visit:
