[Introduction to Tapestry of apache]

A component-oriented framework for creating highly scalable web applications in Java.



 

Java Power

Tapestry pages and components are simple Java POJOs, with easy access to all Java language features and the vast Java ecosystem. Thanks to Java's advanced concurrency API, Tapestry handles requests fast without sacrificing security or stability.

 

Scripting Ease

Tapestry features live class reloading: change your Java code, refresh the browser and see the changes... instantly! Have your cake and eat it too: the speed and depth of Java, the agile development style of Ruby or Python.

 

Super Productivity

Simple POJO classes, streamlined templates, live class reloading, state-of-the-art exception reporting, first-class Ajax support, and a big library of built-in components: Tapestry is designed from the ground up to give you great productivity.

 

The Tapestry framework is a layer that sits between the java servlet container and the Tapestry application. Tapestry is not a stand-alone server; it is a servlet extension that runs in a servlet container (such as Tomcat) or an application server (such as Jboss, Websphere, or WebLogic) that contains a servlet container. A Tapestry application is actually a series of pages composition, and each page is composed of reusable components.

 

Tapestry is a java-based web application framework. Tapestry adopts the concept of components. Programmers can build applications by applying existing components or custom application-related components. Compared with other existing web application frameworks, the application of Tapestry will free programmers from cumbersome and unnecessary low-level code.

 

Tapestry replaces the tag library with a component library, without the concept of a tag library, thus avoiding the problem of combining the tag library and the component. Tapestry is a fully componentized framework. Tapestry only has two concepts of components or pages, so the link jump target is either a component or a page, and there is no redundant path concept. The component name, that is, the object name, the component name and the path name are combined into one.

 

The location of the Tapestry in the overall environment; the application consists of pages of reusable components. The application runs in the application server. To an application server, a Tapestry application is just another type of servlet.

Web applications are usually implemented in three layers, each of which addresses different problems in the application.

Φ The responsibility of the presentation layer is to accept requests and generate HTML responses;

Φ The responsibility of the application layer is to be responsible for all business logic; this layer is usually implemented with EJB;

Φ The responsibility of the database layer is to store data persistently;

 

 

The component logic of Tapestry is complex, and coupled with the OGNL expression and attribute specification mechanism, it is difficult to add annotations.

1. Tapestry is a comprehensive web application framework written in JAVA.

2. Tapestry is not an application server, Tapestry is a framework used in application server.

3. Tapestry is not an application, Tapestry is a framework for creating web applications.

4. Tapestry is not a way of using JSP. Tapestry and JSP can only choose one.

5. Tapestry is not a scripting environment. Tapestry uses a component object model. This is not a simple script, but is used to generate highly dynamic and highly interactive web pages.

 

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326470896&siteId=291194637