Range |
- Application
Under Application-managed Internationalization (AMI) servlets are responsible
to manage (set) invocation context elements using the internationalization
context API. The container suspends internationalization context imported
from the calling process on lifecycle method invocations, including HTTP servlet
requests; to continue propagating this context on subsequent business method
requests, the method must use the API to transfer caller context elements
to the invocation context scoped to the method. Invocation context elements
not set using the API default to the respective elements of the current process
when accessed using the API or when propagated on outgoing business method
requests. Specify Application-managed Internationalization for servlets
having internationalization context management requirements not supported
by Container-managed Internationalization. - Container
Under Container-managed Internationalization (CMI) servlets have read-only
access to the internationalization context API and rely solely on the Web
container to manage invocation context in accordance with the Run as field
of the applicable Container Internationalization attribute. On a service method
invocation, the container scopes the context indicated by the Run as field
to the method; when the method has completed, the container removes this context
from scope. If the servlet is not indicated within a Container Internationalization
attribute, the container scopes the caller context by defualt. Invocation
context elements unavailable to the container default to the respective elements
of the server JVM when accessed using the API or when propagated on outgoing
business method requests.
|