...

Render variable names are case insensitive.

Property: Bindings

Main Article: Property Expressions

The "prop:" binding prefix indicates a property expression binding.

Property expressions are used to link a parameter of a component to a property of its container. Property expressions can navigate a series of properties and/or invoke methods, as well as several other useful patterns. See Component Parameters.

The default binding prefix in most cases is "prop:", which is why it is usually omitted.

Validate: Bindings

Main Article: Component Parameters Forms and Validation

The "validate:" binding prefix is highly specialized. It allows a short string to be used to create and configure the objects that perform input validation for form control components, such as TextField and Checkbox.

...

The list of available translators is configured by the TranslatorSource service.

Asset: Bindings

Main Article: Assets

Assets bindings are used to specify Component Parameters, static content served by Tapestry. By default, assets are located relative to the component class in your packaged application or module. This can be overridden by prefixing the path with "context:", in which case, the path is a context path from the root of the web application context. Because accessing context assets is relatively common, a separate "context:" binding prefix for that purpose exists (described below).

Context: Bindings

Main Article: Assets

Context bindings are like asset bindings, but the path is always relative to the root of the web application context. This is intended for use inside templates, i.e.:

...

Informal Parameters

Main Article: Component Supporting Informal Parameters

Many components support informal parameters, additional parameters beyond the formally defined parameters. Informal parameters will be rendered into the output as additional attributes on the tag rendered by the component. Generally speaking, components that have a 1:1 relationship with a particular HTML tag (such as <TextField> and <input> will support informal parameters.

...

If your component should render informal parameters, just inject the ComponentResources for your component and invoke the renderInformalParameters() method. See Component See Supporting Informal Parameters for an example of how to do this.

...

Parameter Type Coercion

Main Article: Component Parameters Parameter Type Coercion

Tapestry includes a mechanism for coercing types automatically. Most often, this is used to convert literal strings into appropriate values, but in many cases, more complex conversions will occur. This mechanism is used for component parameters, such as when an outer component passes a literal string to an inner component that is expecting an integer.

...