ITC382 11255412 A1A2
From PeacockWiki
| Revision as of 07:40, 26 August 2005 (edit) Trevorp (Talk | contribs) ← Previous diff |
Revision as of 07:42, 26 August 2005 (edit) Trevorp (Talk | contribs) Next diff → |
||
| Line 6: | Line 6: | ||
| Struts, JSP, Tag Libraries, WebWork, and now Tapestry??? Who cares? Just another web-based Java technology to sit in the attic with all the other failed frameworks? You are forgiven for thinking that, until you read their [http://jakarta.apache.org/tapestry/ homepage]. All this talk about simplicity, consistency, efficiency, robustness, scalability? yeah, yeah, yeah, more market-speak, but where are these promises on the sites of [http://struts.apache.org/ struts] or [http://java.sun.com/products/jsp/faq.html JSP]?<br/> | Struts, JSP, Tag Libraries, WebWork, and now Tapestry??? Who cares? Just another web-based Java technology to sit in the attic with all the other failed frameworks? You are forgiven for thinking that, until you read their [http://jakarta.apache.org/tapestry/ homepage]. All this talk about simplicity, consistency, efficiency, robustness, scalability? yeah, yeah, yeah, more market-speak, but where are these promises on the sites of [http://struts.apache.org/ struts] or [http://java.sun.com/products/jsp/faq.html JSP]?<br/> | ||
| Tapestry does not rely on code generation, it uses a JavaBean based object model and a well designed engine for processing HTML templates (using OGNL expressions), creating an extremely flexible framework that completely separates the HTML from Java. Because Tapestry uses its own engine, it allowed the developers to design the engine to handle much of the "glue" code that would normally exist in a Struts solution, reducing the size and complexity of applications, with some pages not needing Java code at all. The engine transparently handles sessions, making your Java code look more like an application rather the typical sterilised unintuitive objects.<br/> | Tapestry does not rely on code generation, it uses a JavaBean based object model and a well designed engine for processing HTML templates (using OGNL expressions), creating an extremely flexible framework that completely separates the HTML from Java. Because Tapestry uses its own engine, it allowed the developers to design the engine to handle much of the "glue" code that would normally exist in a Struts solution, reducing the size and complexity of applications, with some pages not needing Java code at all. The engine transparently handles sessions, making your Java code look more like an application rather the typical sterilised unintuitive objects.<br/> | ||
| - | Althought Tapestry is very young, it is also very mature in the sense it is well thought out, and applicable to a wide range of applications. Being somewhat unusual in its nature, Tapestrys learning curve is unusally steep, requiring the understanding of several open standards, as well as the Tapestry engine itself, but after a short while you discover how much work Tapestry does for you, and how intuitavely it does it. Its use is not wide spread, but its use certainly confirms its power, and its future, finding its way into applications from [http://partnermine.com/ online dating services] to [http://searchapp.usitc.gov/edis3/app governmental search facilities], and to [http://www.theserverside.com/ community forums such as TheServerSide.com]. | + | Althought Tapestry is very young, it is very mature in the sense it is applicable to a wide range of applications. Tapestrys learning curve is unusally steep, requiring the understanding of several open standards, as well as the Tapestry engine itself, you quickly discover how much work Tapestry does for you, and how intuitavely it does it. Its use is not wide spread, but its use certainly confirms its power, and its future, finding its way into applications from [http://partnermine.com/ online dating services] to [http://searchapp.usitc.gov/edis3/app governmental search facilities], and to [http://www.theserverside.com/ community forums such as TheServerSide.com]. |
| {{ITC382_11255412_A1}} | {{ITC382_11255412_A1}} | ||
Revision as of 07:42, 26 August 2005
| Assignment 1: | Journal | Non-Technical Article | Technical Article | Technical Report | Demo App |
Technical Article
Weaving Webapps
Tapestry is an open-source servlet providing a powerful framework for efficiently developing Java Web-Applications.
Struts, JSP, Tag Libraries, WebWork, and now Tapestry??? Who cares? Just another web-based Java technology to sit in the attic with all the other failed frameworks? You are forgiven for thinking that, until you read their homepage. All this talk about simplicity, consistency, efficiency, robustness, scalability? yeah, yeah, yeah, more market-speak, but where are these promises on the sites of struts or JSP?
Tapestry does not rely on code generation, it uses a JavaBean based object model and a well designed engine for processing HTML templates (using OGNL expressions), creating an extremely flexible framework that completely separates the HTML from Java. Because Tapestry uses its own engine, it allowed the developers to design the engine to handle much of the "glue" code that would normally exist in a Struts solution, reducing the size and complexity of applications, with some pages not needing Java code at all. The engine transparently handles sessions, making your Java code look more like an application rather the typical sterilised unintuitive objects.
Althought Tapestry is very young, it is very mature in the sense it is applicable to a wide range of applications. Tapestrys learning curve is unusally steep, requiring the understanding of several open standards, as well as the Tapestry engine itself, you quickly discover how much work Tapestry does for you, and how intuitavely it does it. Its use is not wide spread, but its use certainly confirms its power, and its future, finding its way into applications from online dating services to governmental search facilities, and to community forums such as TheServerSide.com.
| Assignment 1: | Journal | Non-Technical Article | Technical Article | Technical Report | Demo App |
