Migration considerations for the internationalization service

Applications deployed with the internationalization service in versions 4 and later can continue to use the service in later versions with no modification. The packaging and structure of the internationalization context API remain identical across releases. The semantics of the API remain the same as well. Management policies used in Version 4 are semantically equivalent to default policies in versions 5 and later.

In Version 4, the internationalization service did not provide internationalization deployment descriptor policy information to direct how the service manages internationalization context across the various application components. Rather, the service employed the implicit client-side internationalization (CSI) and server-side internationalization (SSI) policies, which dictated how the service managed context according to the type of container that hosts a component. For details, refer to the combined information center for WebSphere Application Server Version 4. Briefly, all server components in Version 4 are SSI, and all EJB client applications are CSI.

In versions 5 and later, the internationalization type setting of all server components is configured to Container by default. The internationalization service assigns the RunAsCallercontainer internationalization attribute by default to any container-managed (CMI) servlet or enterprise bean invocation lacking a container internationalization attribute. As a result, the calls of server components that lack internationalization policy information in the deployment descriptor run under the policy [CMI, RunAsCaller], which is semantically equivalent to the SSI internationalization policy of Version 4; EJB client applications run under the logical policy [AMI, RunAsServer], which is equivalent to the CSI policy of Version 4.

When migrating a Version 4 application to versions 5 or later, it is unnecessary to configure the internationalization deployment descriptor information during application assembly because all component invocations run under semantically equivalent internationalization context management policies.




Related concepts
Internationalization context: Management policies
Related tasks
Assembling internationalized applications
Task overview: Internationalizing application components (internationalization service)
Related reference
Internationalization context API: Programming reference
Reference topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=rin_migration
File name: rin_migration.html