|
|
|
|
The Controller should implement mechanism of configuring application global settings.
Application global settings are used to:
These use cases imply the following requirements for the Controller implementation:
Application global settings information is contained in the basic package metadata. Such settings are declared by the global-settings element within the application description, in the format defined by the Specification in the section 5.1.17. Global Settings. The global settings that must not be involved in reconfiguration of existing application instances are marked with the installation-only="true" attribute.
Application global settings may require uniqueness of their values within some scope. Such settings are marked with uniq attribute that value defines scope of setting value uniqueness. The Controller must validate and ensure uniqueness of such settings values. For details, refer to the 5.2.5 Service Settings section of the Specification.
Values of application global settings may be verified with special verification script declared in the "/application/provision/verify-script" element. If verification script is declared, the Controller may run it itself or provide a user with dialog window where user can click special control for verification, for example, Verify button. A verification script definition may include structured-output element. In this case a script returns report on erroneous values in the form defined by the Specification. The Controller should catch output stream independently of error stream and process it. Also, a verification script may return list of choices for enum setting type, it got from an application. The Controller should cache this list of choices and suggest it for respective setting editing. For details on verification script, refer to the 5.3.2.3 Configuration script output and 5.3.3 Verification Script sections of the Specification.
