使用Vaadin构建企业级AJAX应用框架

1星需积分: 7 162 浏览量更新于2024-07-31 收藏 6.55MB PDF 举报

"Vaadin.pdf 是一个关于 Vaadin 框架的详细文档，适用于最新版本。Vaadin 是一个使用 Java 编写的服务器端 AJAX web 应用开发框架，旨在简化高效用户界面的创建，替代 JavaScript。它提供了一系列即用型的 UI 组件，并且支持自定义组件开发，尤其适合大型企业应用的需求。该框架自2001年起已在生产环境中得到验证，适合构建复杂的企业级应用程序。" 以下是关于 Vaadin 框架的详细介绍： 1. **概述**： Vaadin 是一个基于 Java 的服务器端框架，通过 AJAX 技术实现动态网页交互。它的主要目标是简化开发者的工作，提高可重用性、扩展性和满足大型应用需求。框架的核心特点是提供一系列预置的用户界面组件，以及方便开发者构建自定义组件的架构。 2. **示例应用演示**：文档中包含一个示例应用的逐步解析，帮助读者理解 Vaadin 如何实际运作。通过这个过程，开发者能够快速了解 Vaadin 的基本使用方法和设计模式。 3. **Eclipse IDE 支持**： Vaadin 对 Eclipse 集成开发环境有很好的支持，使得在 Eclipse 中进行 Vaadin 应用的开发更为便捷。文档会介绍如何在 Eclipse 中安装 Vaadin 插件，以及如何配置开发环境。 4. **目标与哲学**： Vaadin 的核心目标是提供一个易用、可扩展的框架，让开发者可以用 Java 直接编写用户界面，避免了传统 web 开发中的客户端脚本编写。其哲学强调代码的简洁和效率，同时注重用户体验。 5. **安装与开始**：安装 Vaadin 包括下载分发包、启动内容浏览器，查看包内容以及运行示例应用。文档详细指导了每一步的操作步骤，包括如何设置开发环境，如导入项目到 Eclipse，以及配置所需的构建工具。 6. **开发环境配置**：配置 Vaadin 开发环境涉及安装必要的库和插件，如添加 Vaadin SDK，设置 Maven 或 Gradle 构建系统，以及创建第一个 Vaadin 应用。 7. **组件库**： Vaadin 提供了一个丰富的组件库，包括按钮、表单、表格、布局管理器等，这些组件都是用 Java 编写的，可以直接在服务器端操作，减少了对客户端浏览器的依赖。 8. **事件处理与数据绑定**： Vaadin 支持事件监听和处理，允许开发者通过 Java 代码响应用户的交互。此外，框架还提供了数据绑定功能，使得数据模型与 UI 组件之间的同步变得简单。 9. **主题与样式**： Vaadin 允许自定义主题，通过 CSS 来改变应用的外观和感觉，以满足各种设计需求。 10. **性能与优化**： Vaadin 在服务器端处理大部分逻辑，通过高效的 AJAX 通信减少客户端负担，但也需要注意优化，例如使用分页策略、延迟加载和缓存技术来提高性能。 11. **部署与安全性**：文档还会涵盖如何将 Vaadin 应用部署到各种服务器平台，以及如何考虑应用的安全性，如认证、授权和防止跨站脚本攻击。通过以上内容，开发者可以获得关于 Vaadin 框架全面的理解，并具备开始构建 Vaadin 应用的基础。无论你是初学者还是有经验的开发者，这份文档都能为你提供宝贵的指导。

Before going into details, we should note that this example source code is complete and does

not need any additional declaratively defined template files to be run. To run the program, you

can just add it to your web application, as explained in Section 4.8, “Setting Up the Application

Environment”.

1.3. Support for the Eclipse IDE

While Vaadin is not bound to any specific IDE, and you can in fact easily use it without any IDE

altogether, we provide special support for the Eclipse IDE, which has become the standard

environment for Java development. The support includes:

• Import the installation package as a QuickStart demo project in Eclipse

• Install the Vaadin Plugin for Eclipse, which allows you to:

• Create new Vaadin projects

• Create custom themes

• Create custom client-side widgets and widget sets

• Edit components with a visual (WYSIWYG) editor

• Easily upgrade to a newer version of the Vaadin library

The Vaadin Plugin for Eclipse is our recommended way of installing Vaadin; the actual installation

package contains demos and documentation that are available also from the website, so you

do not normally need to download and install it, unless you want to experiment with the demos

or try debugging.

Installing and updating the plugin is covered in Section 2.2.5, “Vaadin Plugin for Eclipse” and

the creation of a new Vaadin project using the plugin in Section 2.4.1, “Creating the Project”.

See Section 8.4, “Creating a Theme in Eclipse”, Section 10.2, “Doing It the Simple Way in Eclipse”,

and Chapter 7,

Visual User Interface Design with Eclipse (experimental)

for instructions on using

the different features of the plugin.

1.4. Goals and Philosophy

Simply put, Vaadin's ambition is to be the best possible tool when it comes to creating web user

interfaces for business applications. It is easy to adopt, as it is designed to support both entry-

level and advanced programmers, as well as usability experts and graphical designers.

When designing Vaadin, we have followed the philosophy inscribed in the following rules.

Support for the Eclipse IDE4

Introduction

Right tool for the right purpose

Because our goals are high, the focus must be clear. This toolkit is designed for creating web

applications. It is not designed for creating websites or advertisements demos. For such pur-

poses, you might find (for instance) JSP/JSF or Flash more suitable.

Simplicity and maintainability

We have chosen to emphasize robustness, simplicity, and maintainability. This involves following

the well-established best practices in user interface frameworks and ensuring that our imple-

mentation represents an ideal solution for its purpose without clutter or bloat.

XML is not designed for programming

The Web is inherently document-centered and very much bound to the declarative presentation

of user interfaces. The Vaadin framework frees the programmer from these limitations. It is far

more natural to create user interfaces by programming them than by defining them in declarative

templates, which are not flexible enough for complex and dynamic user interaction.

Tools should not limit your work

There should not be any limits on what you can do with the framework: if for some reason the

user interface components do not support what you need to achieve, it must be easy to add

new ones to your application. When you need to create new components, the role of the

framework is critical: it makes it easy to create re-usable components that are easy to maintain.

1.5. Background

The library was not written overnight. After working with web user interfaces since the beginning

of the Web, a group of developers got together in 2000 to form IT Mill. The team had a desire

to develop a new programming paradigm that would support the creation of real user interfaces

for real applications using a real programming language.

The library was originally called Millstone Library. The first version was used in a large production

application that IT Mill designed and implemented for an international pharmaceutical company.

IT Mill made the application already in the year 2001 and it is still in use. Since then, the company

has produced dozens of large business applications with the library and it has proven its ability

to solve hard problems easily.

The next generation of the library, IT Mill Toolkit Release 4, was released in 2006. It introduced

an entirely new AJAX-based presentation engine. This allowed the development of AJAX applic-

ations without the need to worry about communications between the client and the server.

Release 5 Into the Open

IT Mill Toolkit 5, released initially at the end of 2007, took a significant step further into AJAX.

The client-side rendering of the user interface was completely rewritten using GWT, the Google

Web Toolkit.

IT Mill Toolkit 5 introduced many significant improvements both in the server-side API and in

the functionality. Rewriting the Client-Side Engine with GWT allowed the use of Java both on the

client and the server-side. The transition from JavaScript to GWT made the development and

integration of custom components and customization of existing components much easier than

5Right tool for the right purpose

Introduction

before, and it also allows easy integration of existing GWT components. The adoption of GWT

on the client-side did not, by itself, cause any changes in the server-side API, because GWT is

a browser technology that is hidden well behind the API. Also themeing was completely revised

in IT Mill Toolkit 5.

The Release 5 was published under the Apache License 2, an unrestrictive open source license,

to create faster expansion of the user base and make the formation of a developer community

possible.

Stabilization of the release 5 took over a year of work from the development team. It introduced

a number of changes in the API, the client-side customization layer, and the themes. Many sig-

nificant changes were done during the beta phase, until the stable version 5.3.0 was released

in March 2009.

Birth of Vaadin Release 6

IT Mill Toolkit was renamed as

Vaadin Framework

, or Vaadin in short, in spring 2009. Later IT

Mill, the company, was renamed as Vaadin Ltd. Vaadin means an adult female semi-domesticated

mountain reindeer in Finnish.

The most notable enhancements in Vaadin 6 are the external development tools:

• Eclipse Plugin

• Visual user interface editor under Eclipse (experimental)

The Eclipse Plugin allows easy creation of Vaadin projects and custom client-side widgets. See

Section 2.2.5, “Vaadin Plugin for Eclipse” for details. The visual editor, described in Chapter 7,

Visual User Interface Design with Eclipse (experimental)

makes prototyping easy and new users

of Vaadin should find it especially useful for introducing oneself to Vaadin. Like Vaadin itself,

the tools are open source.

While the API in Vaadin 6 is essentially backward-compatible with IT Mill Toolkit 5.4, the package

names and some name prefixes were changed to comply with the new product name:

• Package name com.itmill.toolkit was renamed as com.vaadin.

•

The static resource directory ITMILL was changed to VAADIN.

•

Client-side widget prefix was changed from "I" to "V".

•

CSS style name prefix was changed from "i-" to "v-".

Other major enhancements in Vaadin 6 are listed in the Release Notes for Vaadin 6.0.0, which

also gives detailed instructions for upgrading from IT Mill Toolkit 5.

Birth of Vaadin Release 66

Introduction

2.1.1. Installing the Distribution Package

You can install the Vaadin installation package in a few simple steps:

1. Download the newest Vaadin installation package from the download page at http://vaad-

in.com/download/.

2. Unpack the installation package to a directory using a decompression program available

in your operating system (see below).

• In Windows, use the default ZIP decompression program to unpack the package

into your chosen directory e.g. C:\dev.

Warning

At least the Windows XP default decompression program and some

versions of WinRAR cannot unpack the installation package properly in

certain cases. Decompression can result in an error such as "

The system

cannot find the file specified.

" This happens because the decompression

program is unable to handle long file paths where the total length ex-

ceeds 256 characters. This occurs, for example, if you try to unpack the

package under Desktop. You should unpack the package directly into

C:\dev or some other short path or use another decompression pro-

gram.

• In Linux, Mac OS X, and other UNIX-like systems, use Info-ZIP or other ZIP software

with the unzip vaadin-6.x.x.zip command.

The files will be, by default, decompressed into a directory with the name

vaadin-6.x.x.

2.1.2. Starting the Content Browser

The Content Browser is your best friend when using Vaadin. It allows you to browse document-

ation and example source code, and run the demo applications. The demo applications

demonstrate most of the core features of Vaadin. You can find the demo applications also at

the vaadin website: http://vaadin.com/demo.

To start the Content Browser, run the start script in the Vaadin installation directory as instructed

below. The start script launches a stand-alone web server running on the local host at port 8888,

and a web browser at address http://localhost:8888/.

The Content Browser will open the default web browser configured in your system. If your default

browser is not compatible with Vaadin the demo applications may not work properly. In that

case launch a supported browser manually and navigate to http://localhost:8888/.

If the Content Browser fails to start, make sure that no other service is using port 8888.

JRE must be installed

You must have Java Runtime Environment (JRE) installed or the batch file will fail

and close immediately. A JRE can be downloaded from ht-

tp://java.sun.com/javase/downloads/index.jsp.

Installing the Distribution Package8

Getting Started with Vaadin

剩余323页未读，继续阅读

草雉旭日

粉丝: 1
资源: 9

使用Vaadin构建企业级AJAX应用框架

Building Modern Web Apps with Spring Boot and Vaadin.pdf

vaadin整合springboot

使用Xtend构建Vaadin UI

android-json-0.0.20131108.vaadin1.jar

android-json:jar:0.0.20131108.vaadin1

java webmvc学习资料

vaadin-maven-plugin爆红

vaadin整合mybatis

springboot vaadin

vaadin官方文档

最新资源