Simple Components | Tapestry 5: Building Web Applications

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents

Tapestry 5: Building Web Applications

4.2 (12)

Tapestry 5: Building Web Applications

4.2 (12)

Overview of this book

Tapestry 5

Tapestry 5

Credits

Credits

About the Author

About the Author

About the Reviewers

About the Reviewers

Preface

Preface

Foreword

Foreword

Free Chapter

Introduction to Tapestry

Introduction to Tapestry

Why is Tapestry Special?

Is Tapestry the Savior in the World of Java Web Development?

Summary

Creating Your Working Environment

Creating Your Working Environment

Install a JDK

Install Maven

Install NetBeans

Installing Eclipse

Installing Tomcat

Configuring the Project in Eclipse

Summary

The Foundations of Tapestry

The Foundations of Tapestry

Tapestry Application is a Set of Interactive Pages

Page Template and Page Class

Using Expansions

Using Components

Passing a Value Between Pages

What Can be Returned From an Event Handler

Tapestry Pages are Pooled

Making a Page Field Persistent

Using Page Activation Context

Different Ways of Defining Components

Structuring the Application

Creating and Using an Application State Object

Was an ASO Already Instantiated?

Summary

Simple Components

Simple Components

Celebrity Collector Project

The Auxiliary Classes

TextField, PasswordField and PageLink

Limiting Access to a Page

Loop, Output and DirectLink

Another Use of PageLink Component

Radio and RadioGroup

Using Enumerations for Radio Component Values

Prefixes: prop and literal

The If and Checkbox Components

Submit Component

More Than One Submit Button

Select Component

Configuring an Application State Object

Summary

Advanced Components

Advanced Components

Grid Component

Tweaking the Grid

Changing the Column Titles

Using GridDataSource

BeanEditForm Component

Tweaking BeanEditForm

DateField Component

Changing the Styles of Grid and BeanEditForm

FCKEditor Component

Summary

User Input Validation

User Input Validation

Adding Validation to Components

Validators

Providing Custom Error Messages

Handling Validation-Related Form Events

Cross-Form Validation

BeanEditForm Validation

Summary

Internationalization and Localization

Internationalization and Localization

Internationalization on the Java Platform

Internationalization in Tapestry

Creating and Using Message Catalogs

Providing a German Message Catalog

Switching Locale

Internationalization of Images

Using Localized Templates

Other Examples of Internationalization

Summary

Creating Custom Components

Creating Custom Components

How to Create a Tapestry 5 Component

Creating the Border Component

Adding a Navigation Menu

Using a Parameter

Unleashing the Power of Select Component

Creating an OptionModel

Creating a SelectModel

Creating a ValueEncoder

Selecting a Celebrity

DateInput Component

Making DateInput a Field

Adding Simple Validation

Creating a Universal Locale Switcher

Creating a Custom Service

Creating a Library of Custom Components

Summary

The Basics of Java for the Web

The Basics of Java for the Web

The Standard Structure of a Java Web Application

The Basics of the Deployment Descriptor

WAR Files Basics

About Java-Enabled Servers

Creating a Real Data Source with db4o

Creating a Real Data Source with db4o

Preparing the Database

The Main Operations

The Final Strokes

Where to Go Next

Where to Go Next

Configuring an Application State Object

Currently, to provide a data source to our pages, we are using an application state object of type MockDataSource, like this:

@ApplicationState
private MockDataSource dataSource;

When we request such an ASO for the first time, Tapestry takes the specified class and creates an instance of it using its no-argument constructor (naturally, such a constructor should exist). It then stores this instance into the session and gives us a reference to it.

All this works okay, but imagine that one day we have created a real data source, and so now we want to have the data source ASO like this:

@ApplicationState
private RealDataSource dataSource;

We would have to find all the references to this ASO and change them then. Not impossible, but this isn't a good design. To avoid this, we create the IDataSource interface, and our MockDataSource implements it. Ideally, we would wish the ASO to be defined in a generic way, like this:

@ApplicationState
private IDataSource...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Tapestry 5: Building Web Applications

Search

Your notes and bookmarks