Comparison between JSP development framework and Servlet-based Tapestry

JSF and Tapestry are both development frameworks based on the page component technology. However, JSF is a JSP Development Framework Based on JSP architecture, which makes development and maintenance very troublesome. Tapestry is different. It is a fully page componentized development framework based on servlet. It is very mature and has launched t4.0-beta2.

The trend of page development towards componentization is becoming more and more obvious. In this regard, tapestry can be said to have guided this direction. Maybe sun is so powerful that jsf will attract everyone's attention as soon as it was born, but as it goes, tapestry's user community is more prosperous than before: http://news.gmane.org/gmane.comp.java.tapestry.user

Tapestry has many great examples, see its official website: http://jakarta.apache.org/tapestry/

If you want to develop web pages, I personally think that jsp/serlvet is the first master. Choosing a framework is a matter of effort. The purpose of the framework is to simplify the development process and improve production efficiency. Typical frameworks include turbine, struts, webwork, jsf, and tapestry.

The choice of frameworks is a long-lasting discussion. Without years of practical experience, it is difficult to make practical evaluations and final choices. I thought turbine was too heavy, and the development speed and running speed were unacceptable. From 2.4M1 to the present, it was almost a year or M !, Starting from running, it's really full of snails. Opening a page has to wait for the browser's Earth to turn to the upper half. This may be due to velocity resolution and no page cache.

There is also scalability and maintainability, which are actually very poor. Like its core class Turbine, it is actually defined as final! Actually, it is not as efficient and fast as the velocity + servlet + filter framework implemented by myself.

Struts and webwork are actually packaged by jsp MVC, so it cannot get rid of the trouble of difficult maintenance of jsp pages. It may be faster to develop, but what about maintenance?

There is also the art workers who have to understand jsp. The actual mvc division of labor is still discounted on the page. As a JSP development framework, JSF draws on the idea of tapestry components to a certain extent, however, many tag packages and definitions in big project applications drive you crazy and drive the machine crazy. estimation has two drawbacks: slow running speed and complex page maintenance.

The last step is tapestry. The only difficulty is to understand its component development method. The transformation is like from process development to OO development, but it doesn't matter to beginners, a piece of white paper is always easy to draw.

Choosing tapestry has the following advantages:

1. the most thorough MVC development framework. The page code is composed of HTML standard tags. The page artist does not need to understand the special tag definition.

2. Reusable Component development saves development resources. One sentence: the easier it is to develop

3. Excellent page transfer development. In the traditional method, activation page flow is implemented based on URLs. In addition to this method, you can also implement page flow like developing common java classes. More importantly, page classes can also be reused.

4. Rich component resources. In addition to officially maintained resources, you can also find a large number of tapestry component libraries.

5. Strong scalability. Tapestry is a real open architecture. To put it bluntly, you can replace it with something you think is uncomfortable.

6. strong vitality and constant self-updating and development. Tapestry4.0 compared with 3.0 is simply another leap, such as support for jdk1.5 Annotations, only this open-source products are currently only seen in a hibernate; support for the portlet JSR-168, and a more compliant with the trend of web development support. In the plan, 4.1 will support static pages. Isn't that another expectation of many developers?

7. Stable tapestry developers. A group of people are developing and supporting the tapestry process.

8. Is tapestry mature? There are already a lot of software and big websites based on tapestry.

The advantages and convenience of tapestry are not clear in two sentences. You need to learn more about it yourself.

1. Learning the basic concepts of JSP: Nine implicit objects
2. JSP data paging instance: MySQL Paging
3. JSP Database Operations routine JDBC-ODBC)
4. Basic preparation for learning JSP: JDK installation and configuration
5. Java Servlet Introduction: Perfect Combination with JSP