16
});
}
}
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.
剩余241页未读，继续阅读
qq_29768425
- 粉丝: 0
- 资源: 1
我的内容管理
展开
最新资源
- AirKiss技术详解：无线传递信息与智能家居连接
- Hibernate主键生成策略详解
- 操作系统实验：位示图法管理磁盘空闲空间
- JSON详解：数据交换的主流格式
- Win7安装Ubuntu双系统详细指南
- FPGA内部结构与工作原理探索
- 信用评分模型解析：WOE、IV与ROC
- 使用LVS+Keepalived构建高可用负载均衡集群
- 微信小程序驱动餐饮与服装业创新转型：便捷管理与低成本优势
- 机器学习入门指南：从基础到进阶
- 解决Win7 IIS配置错误500.22与0x80070032
- SQL-DFS：优化HDFS小文件存储的解决方案
- Hadoop、Hbase、Spark环境部署与主机配置详解
- Kisso：加密会话Cookie实现的单点登录SSO
- OpenCV读取与拼接多幅图像教程
- QT实战：轻松生成与解析JSON数据
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
