Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fix broken links

...

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.

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.

Default Label

...

The BeanEditForm component operates in terms of a BeanModel, which describes the properties, their presentation order, labels and so forth.

...

Next, you must make contributions to the DataTypeAnalyzer or DefaultDataTypeAnalyzer services to match properties to your new name.

...

Finally, we tell the BeanEditForm component about the editor via a contribution to the BeanBlockSource service:

Code Block
java
java
public static void contributeBeanBlockSource(Configuration<BeanBlockContribution> configuration)
{
  configuration.add(new BeanBlockContribution("currency", "AppPropertyEditBlocks", "currency", true));
}

...