Member subsystem properties files

The Member subsystem uses PropertyResourceBundle files to store information specific to locales.

By accessing these properties files, one single JavaServer 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. Each properties files is located in the following directory:

WC_installdir/samples/properties

Type  Command Properties file
Address and address book AddressAdd and AddressUpdate Address.properties AddressBook.properties, and language variations (for example, address_en_US.properties).  The  Address.properties file provides globalization support for the AddressBookForm.jsp file. In the JSP file, you can get the content of the property file by calling the getPropertyHashtable method of ResourceBundleDataBean.  The AddressBook.properties file provides globalization support for the AddressBookForm.jsp file. In the JSP file, you can get the content of the property file by calling the getPropertyHashtable method of ResourceBundleDataBean.
User registration UserRegistrationAdd, UserRegistrationUpdate, and AuditUserRegistration UserRegistration.properties and language variations.  UserRegistration.properties provides globalization support for the UserRegistrationForm.jsp file. In the JSP file, you can get the content of the property file by calling the getPropertyHashtable method of the ResourceBundleDataBean. The AuditUserRegistration task command source code may need to be updated in order to use this information in the property file.
Organizational entity registration and management OrgEntityAddOrgEntityUpdate, OrgEntityManage, and  AuditOrgEntity OrgEntity.properties,  OrgEntityManage.properties, and language variations. T he OrgEntity.properties file provides globalization support for the OrgEntityForm.jsp file. In the JSP file, you can get the content of the property file by calling the getPropertyHashtable method of the ResourceBundleDataBean.  The AuditOrgEntity task command source code may need to be updated in order to use this information in the property file.  The OrgEntityManage.properties file provides globalization support for the OrgEntityManageForm.jsp file. In the JSP file, you can get the content of the property file by calling the getPropertyHashtable method of the ResourceBundleDataBean.

See the sample Java Server Page, UserRegistrationForm.jsp for an extended example. The following example shows fragments of the properties files for French and English, as well as the JSP file.  The objective is to indicate that in English, the label for the state parameter is "State", that it should be displayed, but is not required.  In French, the label is "Departement" (with an accent on the first "e"), but it is not displayed.

From UserRegistration_en_US.properties:

* 100.Label=State
* 100.Displayed=yes
* 100.Required=no

From UserRegistration_fr_FR.properties:

* 100.Label=Departement (with an accent on the first "e") 
* 100.Displayed=yes
* 100.Required=no

From UserRegistrationForm.jsp:

<% if (((Boolean)hshState.get(ECUserConstants.EC_RB_DISPLAYED)).booleanValue())
{ %>
<TD ALIGN=right><FONT SIZE=2>
<% if (((Boolean)hshState.get(ECUserConstants.EC_RB_REQUIRED)).booleanValue())
{ %> <B> <% } %>
<%= hshState.get(ECUserConstants.EC_RB_LABEL) %></B></FONT>
</TD>
<TD>
<INPUT TYPE="text" NAME="<%= StateURL %>"
VALUE="<%= strState %>" SIZE="20" MAXLENGTH="20">
</TD>