![]() |
Internationalization context consists of a fixed-length list (array) of locales and a time zone (where a locale is an instance of the java.util.Locale class and time zone is an instance of the java.util.SimpleTimeZone class). Refer to the Java SDK API documentation for a complete description of each type.
Note: For this release, the Internationalization Service does not support Java SDK TimeZone types other than java.util.SimpleTimeZone. Unsupported TimeZone types silently map to default SimpleTimeZone when supplied to service API methods.Enterprise JavaBean applications use the service to access and manage the following types of Internationalization context:
- Caller context
- Caller context is a locale list and time zone that propagates from calling application components on remote business methods and requests; it is the context associated with an incoming request. Caller context is accessible within all application components, but is manageable neither declaratively nor programmatically and defaults to that of the process (for example, java.util.Locale.getDefault() or java.util.SimpleTimeZone.getDefault()) whenever it is unavailable.
- Invocation context
- Invocation context is a locale list and time zone that propagates to target application components on remote business methods; it is the context under which a component or business method executes. Invocation context is manageable both declaratively and programmatically according to the applicable Internationalization Service context management policies. In particular, these polices specify API access restrictions, how invocation context propagates on remote requests, and the context under which a target request executes.
To make these terms more concrete, imagine a simple JavaBean application having a client that invokes remote bean method, myBeanMethod(). On the client-side, the application can utilize the service to access caller or invocation context. When the application calls myBeanMethod(), the service attaches the invocation context to the outgoing request. On the server-side, the service detaches the caller context from the incoming request and makes it available to the implementation of myBeanMethod(), which can utilize the Internationalization service API to access it.
These terms are important in describing how the WebSphere Application Server manages Internationalization context on behalf of an application.
Related reference... | |
Internationalization context management | |
Thread association considerations | |
The JNDI environment | |
Internationalization context application programming interface | |
Handling exceptions | |
View PDF file... | |
To view a PDF file containing this article and related articles, click: | |
![]() | |