Apache Wicket 7 教程：构建无痛Web应用

需积分: 11 36 浏览量更新于2024-07-18 收藏 4.35MB PDF 举报

"Apache Wicket 7教程：从入门到精通" Apache Wicket 是一个开源的Java Web开发框架，它以其组件化和声明式编程模型著称，使得开发者可以免于编写大量的JavaScript代码。本教程适用于希望学习或深入了解Wicket 7版本的开发者，特别是后端程序员，它将帮助他们更高效地构建Web应用。 1. **简介** Apache Wicket 提供了一个直观的编程模型，专注于组件和页面的生命周期，使得开发人员能够专注于业务逻辑，而不是处理低级别的HTML和JavaScript细节。 2. **如何使用示例代码** 教程中包含的示例代码旨在帮助学习者快速上手。通过实践这些例子，读者可以理解Wicket的工作原理和最佳实践。 3. **为什么学习Wicket？** - **Spaghetti代码说再见**：Wicket通过组件化的思想，避免了Web开发中的“面条代码”，使得代码结构更加清晰。 - **组件化框架概述**：Wicket与其他MVC框架不同，它以组件为中心，每个组件都有自己的状态和生命周期。 - **组件化框架的优势**：提高了代码复用性，简化了测试，并允许更轻松地进行UI更新。 - **Wicket与其他框架的比较**：Wicket在易用性和灵活性方面有其独特之处，如对HTML的直接支持和对服务器端状态的管理。 4. **Wicket说“你好，世界！”** - **Wicket的分发和模块**：了解Wicket的基本组成和如何设置项目环境。 - **应用程序配置**：学习如何配置Wicket应用程序，包括初始化和配置设置。 - **HomePage类**：创建第一个Wicket页面，通常从HomePage类开始。 - **Wicket链接**：掌握创建和使用链接来导航页面。 5. **Wicket作为页面布局管理器** - **页眉、页脚、侧边栏和内容**：学习如何组织页面结构，创建可重用的布局组件。 - **继承机制**：利用Wicket的继承特性来实现通用布局和子页面的定制。 - **分割并征服**：通过组件划分，提高代码的可维护性和复用性。 - **使用wicket:extend标签进行标记继承**：了解如何通过继承和扩展来简化HTML模板的编写。 6. **保持对HTML的控制** - **隐藏或禁用组件**：根据程序逻辑动态控制组件的可见性和可交互性。 - **修改标签属性**：自定义HTML元素的属性，如样式、类等。 - **生成标签ID**：Wicket自动管理组件的ID，确保它们在DOM中的唯一性。 - **使用WebMarkupContainer创建内联面板**：创建不占DOM节点的容器，方便嵌入复杂结构。 - **处理标记片段**：学习如何使用片段来组织和重用HTML代码。 - **添加头部内容**：向HTML文档的<head>部分添加CSS和JavaScript资源，以实现页面样式和功能。通过这个教程，读者将全面掌握Apache Wicket 7的核心概念和技术，包括组件设计、页面布局、HTML控制以及应用程序配置。无论是初学者还是有经验的开发者，都能从中受益，提升Web开发的效率和质量。

});

}

In the example above we used a version of which takes as input the class of the targetsetResponsePage

page. In this way a new instance of will be created each time we click on the link. The otherAnotherPage

version of takes in input a page instance instead of a page class:setResponsePage

@Override

void onClick() { public

//we redirect browser to another page.

AnotherPage anotherPage = AnotherPage();new

setResponsePage(anotherPage);

}

The difference between using the first version of rather than the second one will besetResponsePage

illustrated in , when we will introduce the topic of stateful and stateless pages. For now, we canchapter 8

consider them as equivalent.

Wicket comes with a rich set of link components suited for every need (links to static URL, Ajax-enhanced links,

links to a file to download, links to external pages and so on). We will see them in .chapter 10

We can specify the content of a link (i.e. the text of the picture inside it) with its method

. This method takes in input a generic Wicket model, which will be the topic of setBody

.chapter 11

4.5 Summary

In this chapter we have seen the basic elements that compose a Wicket application. We have started preparing

the configuration artifacts needed for our applications. As promised in , we needed to put in place justchapter 2.4

a minimal amount of XML with an application class and a home page. Then we have continued our “first contact”

with Wicket learning how to build a simple page with a label component as child. This example page has shown

us how Wicket maps components to HTML tags and how it uses both of them to generate the final HTML

markup. In the last paragraph we had a first taste of Wicket links and we have seen how they can be considered

as a “click” event listener and how they can be used to navigate from a page to another.

5.2 Here comes the inheritance!

The need of ensuring a consistent layout across our pages unveiled a serious limit of the HTML: the inability to

apply inheritance to web pages and their markup. Wouldn't be great if we could write our layout once in a page

and then inherit it in the other pages of our application? One of the goals of Wicket is to overcome this kind of

limit.

Markup inheritance

As we have seen in the previous chapter, Wicket pages are pure Java classes, so we can easily write a page

which is a subclass of another parent page. But in Wicket inheritance is not limited to the classic object-oriented

code inheritance. When a class subclasses a it also inherits the HTML file of the parent class. ThisWebPage

type of inheritance is called markup inheritance. To better illustrate this concept let's consider the following

example where we have a page class called with the corresponding HTML fileGenericSitePage

GenericSitePage.html. Now let's create a specific page called where users can check outOrderCheckOutPage

their orders on our web site. This class extends but we don't provide it with anyGenericSitePage

corresponding HTML file. In this scenario will use GenericSitePage.html as markup file:OrderCheckOutPage

Markup inheritance comes in handy for page layout management as it helps us avoid the burden of checking that

each page conforms to the site layout. However to fully take advantage of markup inheritance we must first learn

how to use another important component of the framework that supports this feature: the panel.

If no markup is found (nor directly assigned to the class, neither inherited from an

ancestor) a is thrown.MarkupNotFoundException

Panel class

Class is a special component which lets us reuse GUIorg.apache.wicket.markup.html.panel.Panel

code and HTML markup across different pages and different web applications. It shares a common ancestor

class with WebPage class, which is :org.apache.wicket.MarkupContainer

剩余226页未读，继续阅读

yzx_2008

粉丝: 0
资源: 5

Apache Wicket 7 教程：构建无痛Web应用

wicket 官方JAVA教程

Wicket 入门

Wicket中文开发指南

cheesr-javaee:一个集成Java EE和Wicket的教程项目

wicket开发指南

wicket_training

hello-wicket

apache-wicket-1.3.0.zip_wicket

wicket官方文档源代码

wicket例子和开发指南

最新资源