Page History

...

The default ordering for properties is in the order in which the getter methods for the properties are defined. When a super-class defines edittable editable properties, those are ordered before sub-class properties.

...

For a class, Tapestry will select the public constructor with the most parameters. If this is not desirable (for example, if you get an exception), then place the @Inject annotation on the constructor Tapestry should use.

...

In some cases, a property may be updatable and of a supported type for editing, but should not be presented to the user for editing: for example, a property that holds the primary key of a database entity. In such a case, the @NonVisual annotation may be applied to the property (either the getter or the setter method).

...

If desired, additional validation may be specified using the @Validate annotation. See Input Validation.

Property ordering

By default, the order in which properties are presented is as defined above (order of the getter method). This can be overridden using the ReorderProperties class annotation.

...

  <t:beaneditform  object="bean" model="model"/>

...