Java Properties Resource Wizard Page

• Resource File Type: The generated resource file(s) where externalized objects are inserted will be of this type.



• Resource File Frequency: Project means there will be only one file, while Source File means each individual source file where strings are externalized will receive its own corresponding resource file.



• Tag Library: Select the tag library used by your JSP project. This list is only displayed if the current Rule Set is HTML and you have selected properties in the Resource File type field. Options are currently JSTL, struts, and none.



• Retrieval Method: The method signature your program uses to retrieve resources from a resource file. For example, in Java, the call might be: myBundle.getResourceText("somekey"). In this case, you would enter myBundle.getResourceText("[key]") in the Retrieval Method field.



• Use/Generate Static Retrieval Class: Check this box to instruct Globalyzer to generate a locale-sensitive string retrieval class to access your Java properties file. To use this framework, enter the method and parameters in the Retrieval Method field in one of two forms: with only the "[key]" parameter, or with an additional locale parameter. Then, fill in the following two fields with the required information.



• Retrieval Class Name: Name of the static Java retrieval class that Globalyzer will create in the same directory as your properties file. If this field is left blank, Globalyzer will use the name of your Scan to create the retrieval class. Once created, the class name will be prepended to the Retrieval Method during string externalization.



• Retrieval Class Package: Name of the retrieval package. This will be used to create the import statement that will be inserted at the top of all Java files in which string externalization occurs.



• String Key Format: This field displays the current format for the resource keys that Globalyzer creates during string externalization. Click the Edit Format button to change the format, allowing you to completely customize your resource keys.



• String Key Next ID: Initially set to 1, this field is incremented each time you externalize a string, and is used as the ID part of the String Key Format. In this way, Globalyzer maintains uniqueness across all resource keys.



• Share Strings: Allow the sharing of keys for identical strings.



• Externalized String Comment: This will be used if you choose to add a comment after externalizing a string. Select Window=>Preferences=>Globalyzer and check Automatically Insert Externalized String Comment.



• Resource File Path: This is where your resource file is stored. Add a name if you don't already have a file. In the case where Resource File Frequency is set to Source File, Globalyzer will create multiple resource files, with names that correspond to the source filenames. For example, for a file named SwingTest.java, Globalyzer will create a resource file name SwingTest.properties to hold its externalized strings.



• Resource File Encoding: Set the file encoding of the resource file. Globalyzer will assume all your resource files of this type are the same encoding, although it will ensure that if a resource file has BOM bytes (bytes at the beginning of the file that indicate encoding), it will access the file properly, regardless the Project's Resource File Encoding setting. To see the encoding of an individual file, right-click on the file in the Project Explorer view and select Properties.