Configuration with properties

In the configuration file form-engine.properties, which must be stored direct in the classpath, some settings can be made that determine the default behaviour of forms. The most important thereof will be presented here.

Inputs result in a form dynamic changes of different aspects in this form. So the validator of other components can be re-executed if the validation depends on the modified component or the visibility of a component is affected. To reduce the resource requirements for the execution of forms, are the dynamic analysis of the dependencies are not enabled by default for all aspects. By properties thus default configurations can be changed.

• engine.dynamic-validation determines whether validator of components, which consider the condition of other components, will be run again if changes are made to these components. For example this can be a change in value by the user or by a calculator.
  Default value: true
• engine.dynamic-readonly determines whether if components are enabled, that depends on the content or condition of other components, to be dynamically adjusted, if changes are made to the other components. Default value: false, so that the read-only state is determined only at the initial loading of the form instance.
• engine.dynamic-hidden determines whether the visibility of components that depend on the content or condition of other components to be dynamically adjusted when changes are made to the other components. Default value: false, so that the hidden-state is determined and set only at the initial loading of the form instance.

To dynamically evaluate all aspects of the form, the default settings as described below. These settings can also be overridden for each form definition on the same attributes.

engine.dynamic-validation = true
engine.dynamic-readonly = true
engine.dynamic-hidden = true

Other important settings are the encoding and the default locale.
If no locale is specified for translation and presentation the system encoding is used normally. Since this is not always under control of the application developer, the default locale can be set for the form content over the property defaultLocale.

With Ajax requests the page encoding of the output side is often unknown, or rather the browser used in the absence of encoding declaration in response different encodings. By property pageEncoding can be specified which encoding to be sent for Ajax requests in response header. This should correspond to the usual encoding of the web application.

engine.pageEncoding=UTF-8
engine.defaultLocale=de

All properties are documented in the class EngineProperties. The javadoc documentation is contained in the distribution archive available in the download area.