The internationalization type of the message-driven bean.
The internationalization type of a message-driven bean indicates whether
the bean or the hosting EJB container will manage internationalization context
on business method invocations. For message-driven beans the internationalization
type setting can be configured to Application or Container,
and defaults to Container. The setting applies to all business methods of
a message-driven bean.
Select whether the message-driven bean will employ Application or Container
internationalization context management using the Internationalization
Type drop-down menu.
Note: In this release, messages received by message-driven bean
onMessage() invocations lack internationalization context, meaning that caller
context elements are unavailable and always default to the elements of the
server JVM, regardless of the internationalization type or applicable container
internationalization attribute.
Default |
Container |
Range |
- Application
Under Application-managed Internationalization (AMI) a message-driven
bean is responsible to manage (set) invocation context using the internationalization
context API. The container suspends internationalization context imported
from the calling process on business method invocations; to continue propagating
this context on subsequent business method requests, a method must use the
API to transfer caller context elements to the invocation context scoped to
that 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 message-driven beans having internationalization
context management requirements not supported by Container-managed Internationalization. - Container
Under Container-managed Internationalization (CMI) a message-driven
bean has read-only access to the internationalization context API and relies
solely on the container to manage invocation context in accordance with the Run
as field of the applicable Container Internationalization attribute. On
a business method request, 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 bean method is not indicated within a container
internationalization attribute, the container scopes the caller context by
default. Invocation context elements unavailable to the container default
to the respective elements of the current JVM when accessed using the API
or when propagated on outgoing business method requests.
|