Apache Wicket 完全指南：8.x版本详解

需积分: 10 88 浏览量更新于2024-07-20 收藏 4.47MB PDF 举报

Apache Wicket User Guide Reference Documentation是一本专门针对Apache Wicket框架的免费在线参考手册。该文档由多位经验丰富的开发者Andrea Del Bene、Martin Grigorov、Carsten Hufe等人编撰，适用于Wicket 8.x版本。本书旨在为开发者提供深入理解和使用的指导，帮助他们充分利用Wicket进行Web开发。首先，章节1"Introduction"介绍了Apache Wicket框架的基本概念，引导读者了解其在Web开发中的地位以及为什么选择这个框架。Wicket以其组件导向的设计闻名，这在第3章"Component Oriented Frameworks - an Overview"中详细阐述，强调了组件化架构在简化页面开发、提高代码复用性和维护性方面的优势。在"3.4 Wicket vs the other Component Oriented Frameworks"部分，作者比较了Wicket与其他组件化框架的区别，突出了Wicket的独特之处，如其易于学习和灵活的布局管理能力。第4章"Wicket says Hello World!"详细介绍了如何开始使用Wicket，包括安装和配置Wicket应用程序，创建基础的HomePage类，以及如何运用Wicket链接。这些步骤是每个新用户入门的重要部分。章节5"Apache Wicket as a Page Layout Manager"深入探讨了Wicket在网页布局中的应用，如使用继承来管理头部、脚部、侧边栏等内容区域，并展示了如何利用`wicket:extend`标签实现标记继承。通过这些技术，开发者能够轻松地构建复杂的页面结构。在第6章"Keeping Control over HTML"，作者讨论了如何在Wicket中精细控制HTML输出，包括隐藏或禁用组件、修改标签属性、自动生成id以及使用WebMarkupContainer创建内联面板等。此外，章节还涵盖了如何处理和管理标记片段，这对于确保代码的可维护性和可重用性至关重要。总结起来，Apache Wicket User Guide Reference Documentation提供了全面且实用的教程，无论是对初学者还是有经验的开发人员，都能从中获取到开发高质量Web应用所需的知识和技能。通过阅读这本书，读者可以掌握如何利用Wicket的优势，实现高效、灵活和可扩展的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.

Like many other Wicket components, is lambda-friendly and comes with a factory method called Link onClick

which leverages lambda expressions to specify handler method:

public class HomePage WebPage {extends

HomePage(){public

add(Link.onClick( , () -> setResponsePage(AnotherPage.class));"id"

}

The lambda expression is converted into a , which isorg.apache.wicket.lambda.WicketConsumer

basically a serializable version of (we will see later why we need it to bejava.util.function.Consumer<T>

serializable).

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

剩余241页未读，继续阅读

LuckChouDog

粉丝: 58
资源: 31

Apache Wicket 完全指南：8.x版本详解

创建并扩展Apache_Wicket_Web应用.doc

apache-wicket-1.3.0.zip_wicket

Apache Wicket User Guide

apache-wicket

apache-wicket-7

让Apache_Shiro保护你的应用.pdf

apache-wicket-jee-example:此源代码对应于博客系列“ Apache Wicket＆JEE”，网址为-apache source code

apache-wicket-1.5.11.zip

apache-wicket-1.4.17.tar.gz

wicket_workshop:使用 Apache Wicket、Spring Framework 和 Google Guice 的示例 Web 应用程序

最新资源