Tapestry 5：Java快速Web应用开发指南

Apache

Tapestry

需积分: 10 45 浏览量更新于2024-07-21 收藏 11.18MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

《Tapestry 5：快速Java Web应用开发》是由Igor Drobiazko撰写的一本专业书籍，它是作者的最新力作，着重介绍Apache Tapestry 5.2及其在Web应用开发中的优势。本书旨在帮助开发者提升生产力，利用Tapestry的特性实现无代码开发、不间断开发流程，并提供即时反馈。Tapestry的核心概念包括面向对象编程、开发者友好性、避免XML配置、 inversion of control（IoC）、可测试性、扩展性和插件式架构。书中首先介绍了Tapestry的基本理念，它如何通过减少代码量、简化开发过程来提高效率。章节1.1详细阐述了Tapestry如何通过代码省略功能，允许开发者专注于业务逻辑，而非底层细节。非停开发意味着开发人员可以迅速迭代，无需频繁编译和部署。同时，Tapestry的反馈机制有助于开发者及时发现问题并进行调整。接着，作者概述了Tapestry的主要概念，强调其对象导向的设计，使得应用程序的结构清晰，易于维护。此外，Tapestry提倡使用友好的API，而非繁琐的XML配置，这极大地减轻了开发者的负担。Inversion of Control（IoC）原则使得控制权反转，有利于模块化和松耦合，便于单元测试和模块间的解耦。第1.3节深入探讨了Tapestry应用的结构，包括页面组织和组件的使用。Tapestry页面不仅仅是HTML，而是结合业务逻辑的动态组件集合。在创建Tapestry页面时，1.4节指导读者如何入手，而1.5部分则重点讲解如何使用内置的If组件进行条件处理，以及如何自定义组件以满足特定需求，如创建布局组件。《Tapestry 5：快速Java Web应用开发》是一本实用的指南，涵盖了从入门到进阶的Tapestry 5.2技术，适合希望采用Tapestry框架进行高效Web开发的Java开发者阅读。通过这本书，读者可以深入了解Tapestry的核心理念，掌握其实现快速、可扩展和灵活应用的方法。

资源详情

资源推荐

Introducing Tapestry

1.2.1 Object-orientation

In object-oriented (OO) programming, objects have two fundamental characteristics: they

are stateful and have behavior. In Java, an object stores its state in fields and exposes

its behavior through methods. Because web-applications are multi-threaded, you have to

unlearn object-oriented programming. An application server could be handling thousands

of requests from individual users, each in their own thread, and each sharing the exact

same objects. You can't store data inside a shared singleton objects, for example a servlet,

because this data is shared between multiple threads. Any value stored in an instance

field for one client will almost immediately be overwritten with a value for another client.

Frequently such errors only appear in production as there's usually only a single client

during development time.

Tapestry shields you from the multi-threaded aspects of web application development.

Tapestry manages the life-cycle of your page and component objects, reserving particular

objects to particular threads so you never have to think twice about threading issues. In

Tapestry you still can program in terms of object-orientation without caring about the

environment your objects are living in.

1.2.2 Developer friendliness

Tapestry is a Java framework, so its ambition is to make life of Java web developers easier.

To get started with Tapestry, you only need a Java IDE for writing Java code and a text

or WYSIWYG editor for templates. The competing frameworks are praising the existing

graphical tools which simplify development and deployment of web applications. These

tools are reputed to enable managers to create web applications without any programming

skills, just by clicking buttons and using drag-and-drop functionality. Tapestry's approach

is different. The framework was designed to make people who possess programming skills

highly effective and efficient. Because of this, there is much less of a need and dependence

on framework specific development tools and graphical editors.

Everybody is speaking about the Separation of Concerns principle, but only few

technologies provide you the capability to enforce it. With Tapestry you can work

on a specific aspect of your application without significantly impacting other parts of

the application. For example, a HTML designer can create templates for pages and

components because they are so close to ordinary HTML, without all the cruft and

confusion seen in JavaServer Pages. Java developers can focus on application logic,

relying on their HTML gurus for the design.

1.2.3 Avoiding XML configuration

Many Java frameworks make extensively use of XML to configure applications. Probably

the most prominent examples are Struts, JavaServer Faces and Spring. The main problem

Purchased by Christopher Dodunski, ChrisFromPayPal@christopher.net.nz #4141314-

Introducing Tapestry

with XML configuration files is that those often reference class names, or even method

names, that may be refactored (renamed or moved) and the IDE may not be able to keep

the files synchronized. Furthermore, because XML is quite verbose, sooner or later the

configuration files will be hard to maintain.

For most Java programmers it is far more natural to write Java code than to declare the

behavior of the application in XML files. XML is just a suboptimal way to describe Java

operations like instantiating classes and invoking methods on those classes. So, one of the

central concepts in Tapestry 5 is to eliminate XML and build an equivalent system around

simple objects and methods. This system is called Tapestry IoC, a built-in Inversion of

Control container. Based on a handful of naming conventions and annotations Tapestry

IoC allows you to configure your application programmatically, instead of declaring a big

chunk of XML.

1.2.4 Inversion of control

As you already learned, page and component classes in Tapestry are pure POJOs (Plain

Old Java Objects). Contrary to most other web frameworks, you are not required to

extend a framework specific superclass or implement an interface to be able to access the

framework's functionality. Tapestry uses a different approach allowing you to inject the

needed functionality into pages and components. The inner construction of the Tapestry

framework is based on Inversion of Control (IoC), a design approach that allows a system

to be fabricated from many small pieces. Tapestry IoC is a sub-project of Tapestry that

acts as a container for objects, known as services. Don't worry if you a not familiar

with Inversion of Control, in chapter 15 you will get a complete explanation with many

examples. For now it is sufficient to consider Tapestry IoC as a part of the framework

which magically injects services, pages or components into your classes. This injection is

guided by annotations, as shown in the following example.

Listing 1.1 Injecting services, pages and components

public class InjectDemo {

@InjectPage

private MyPage page;

@InjectComponent

private MyComponent component;

@Inject

private HttpServletRequest request;

...

Purchased by Christopher Dodunski, ChrisFromPayPal@christopher.net.nz #4141314-

Introducing Tapestry

all threads giving you the illusion of pages being exclusively used by incoming requests.

How is that possible considering the fact that Tapestry pages are stateful objects? As part

of the class transformation process, all mutable fields of a page are converted into an access

against a per-thread Map. Assigning a value to a mutable field results in writing the value

into the Map. By default, all the values of the per-thread Map are discarded at the end of the

request. This way there is no need to store the entire page instance along with its state and

the huge component structure in the session. Of course, Tapestry provides a way to persist

a value assigned to a page's mutable field between requests. If a field has been marked as

persistent, it's value is not discarded at the end of the request but is stored in the session.

Storing only few values of persistent fields the session instead of entire page's structure is

a huge improvement for scalability as much less session data needs to be replicated around

the cluster nodes. More information on Tapestry's scalability follow in chapter 4.

The most part of Tapestry framework get along well without using HttpSession.

Tapestry also provides you with features that allow you to avoid using session. For

example, the page activation mechanism, described in chapter 3, allows you to store page's

state in URLs. Doing so, you again minimize the usage of session.

1.2.7 Plug-and-play nature

The framework behind Tapestry is designed to build modular web applications. The

built-in IoC container allows you to break a monolithic WAR file into several modules,

each responsible for a certain functionality. These modules can be used as lego bricks to

assemble an application from independent JAR files. Tapestry's modularity facilities can

be used to extend an existing application with new functionality without changing the code

of the application. For example you might create a module which exposes the functionality

of your web application as web services. Tapestry supplies the facility which allows you

to drop a new module on the classpath, restart your server and immediately use the new

functionality.

Another frequent use case is delivering the same application to several customers. In

such a case you often have a problem that a special requirement of a customer conflicts

with a special requirement of another customer. If you include these special wishes into

the application, it will become bloated sooner or later. What you need is a feature that

allows you to extend your application without changing it. This is where your decision

to write web application with Tapestry pays off. Such a requirement is amazingly easy to

implement using Tapestry, but might be a huge problem with other frameworks.

Now that we have learned the basic concepts behind Tapestry, let's explore a typical

structure of a Tapestry application.

Purchased by Christopher Dodunski, ChrisFromPayPal@christopher.net.nz #4141314-

剩余491页未读，继续阅读

bonbonyu

粉丝: 0
资源: 7

Tapestry 5：Java快速Web应用开发指南

tapestry-bin-5.1.0.5

Tapestry5和jQuery集成tapestry5-jquery.zip

springboot集成 tapestry

tapestry介绍

Tapestry内部工作原理

tapestry框架

java常用的框架有哪些

Error creating bean with name 'sessionFactory-his' defined in class path resource

Javaee框架结构

帮我写一篇题目是毕业后你喜欢住在哪个地方，大城市还是小城镇?的英语作为

用verilog实现一个STUMPS架构

数据结构实验报告(集合)

MythwareStudentHacker-main.zip

《金智慧RFID高校固定资产管理平台解决方案》.doc

大连东软信息学院在广东2021-2024各专业最低录取分数及位次表.pdf

湖南财政经济学院在广东2021-2024各专业最低录取分数及位次表.pdf

上海立信会计金融学院在广东2021-2024各专业最低录取分数及位次表.pdf

山西大学在广东2021-2024各专业最低录取分数及位次表.pdf

无感Foc电机控制,算法采用滑膜观测器，启动采用Vf，全开源c代码，全开源，启动顺滑，很有参考价值

最新资源