Use this page to specify which internationalization context the EJB container will scope to enterprise bean business method invocations.
By default, the EJB container scopes the caller's internationalization context to business method invocations of enterprise beans configured to the Container internationalization type. To override this default scoping behavior, create and configure at least one Container Internationalization attribute.
A Container Internationalization attribute associates business methods of those enterprise beans that employ container-managed internationalization to one of three internationalization contexts: the Caller context, the Server context, or the context specified in the attribute. For each method listed in the attribute, the container scopes the internationalization context that is specified in the attribute's Run as field.
Use the information below to configure new and existing Container Internationalization attributes.
Default | Caller |
Range | Valid values are Caller, Server, and Specified |
More information about valid values follows:
The container invokes the attribute's methods with the locales and time zone of the incoming client request. For any missing context element, the container supplies the corresponding default element of the server Java Virtual Machine (JVM). Select Caller when you want bean methods to execute under the invocation context of the client request.
The container invokes the attribute's methods with the default context elements of the server JVM. Select Server when you want bean methods to execute under the invocation context of the server JVM.
The container invokes the attribute's methods with the context elements specified in the attribute's Locales and Time zone ID fields. Select Specified when you want bean methods to execute under the invocation context specified in the attribute. Be sure to complete the Locales and Time zone ID fields. You can add information about the group of specified context elements in the Description field.
Enter a valid time zone ID. A valid ID represents any time zone supported by java.util.TimeZone. Specifically, an ID can be any of the IDs that appear in the list of time zone IDs returned by method java.util.TimeZone.getAvailableIds(), or a custom ID having the form GMT[+|-]hh[[:]mm]; for example, America/Los_Angeles and GMT-08:00 are valid time zone IDs.
Enter the language code of the new locale. Ideally, language code is one of the lower-case, two-character codes defined by ISO-639. Language code is not restricted to ISO codes and is not a required field; however, a valid locale must contain either a language code or a country code.
Enter the country code of the new locale. Ideally, country code is one of the upper-case, two-character codes defined by ISO-3166. Country code is not restricted to ISO codes and is not a required field; however, a valid locale must specify either a language code or a country code.
Enter the variant of the new locale. Variant is not a required field and serves only to supplement the Language code and Country code fields according to application- or platform-specific requirements.