Sample: Member subsystem properties files
The Member subsystem uses PropertyResourceBundle files to store information specific to locales.
By accessing these properties files, one single Java Server Pages file can display different language requirements. For example, there is no personal title in Korean. Accordingly, the Korean version of the properties file associated with the AddressAdd and AddressUpdate commands would indicate this variation.
More generally speaking, these properties files can be used to specify the labels to use for each parameter, including whether a label is mandatory, or used at all in a given language. Furthermore, the properties files can be used to create drop-down lists, define tokens that are used repeatedly, and it can set some HTML formatting parameters.
The settings you put into a properties file do not actually affect the system behavior. For example, setting a parameter as mandatory causes it to appear on the page in a bold font, but does not actually cause the user's input to be checked. To check the user's input requires that the appropriate task command be modified.
The following properties files are associated with commands in the Member subsystem. The default properties files are located in the following directory:
workspace_dir/properties
Type | URL | Properties file |
---|---|---|
Address and address book | AddressAdd and AddressUpdate |
|
User registration | UserRegistrationAdd, UserRegistrationUpdate, and AuditUserRegistration |
|
Organizational entity registration and management | OrgEntityAdd, OrgEntityUpdate, OrgEntityManage, and AuditOrgEntity |
|