Skip to main content

Localization/Internationalization in oracle adf

By

Internationalization and Localization are means of adapting aplication to different languages, regional differences and technical requirements of a target market.

Internationalization is the process of designing a software application so that it can potentially be adapted to various languages and regions without engineering changes. Localization is the process of adapting internationalized software for aspecific region or language by adding locale-specific components and translating text.
Follow below steps for doing localization.

1. Create .properties files as per the locales required in your application.
For demo purpose i created german and english locale properties file, one main file is required which will congtain all labelsSo total 3 properties files are there.
For property file creation ViewController->New->General->File





InterBundle.properties file is the main properties file and for the same labels 2 different files are created one is for english and another is for germen locales.



2.Create one jsff page and add some input texts with labes from properties file.


here we have to specify only main properties file, in our case it is InterBundle.properties. On run time depends on locale it will pic en or de. To look nicer i added some specing and style.Observe the label value which will come based on locale at runtime.

3. Now you can create one taskflow and drop this jsff as default view activity. In one jspx drag taskflow as region.

4. last and most important setting we have to do is in the facs-fonfig.xml file.
Go to Overview section -> Application -> Locale Config


bydefault there will be no value in Default Locale as well as in Supported locale section. Now u can add the locales for which u need to support.de_DE is code for germen language and en is code for english language read by the browser.
It's source code looks like.



5. Now change your browser settings to support german (de-DE).
In IE follow below steps
Tools->General->Language

Here u can add multiple languages and move it up and down as per your prefrences.
Finally run the jspx page.
Chrome showing English as default locale is en.

And for IE it is showing Germen(DE) as localization is germen.



Comments

Post a Comment

Popular posts from this blog

The file store "WLS_DIAGNOSTICS" could not be opened

By
WLS_DIAGNOSTIC ERROR weblogic.store.PersistentStoreException: [Store:280073]The file store "WLS_DIAGNOSTICS" could not be opened because it contained a file with the invalid version 1. A file of version 2 was expected. When you get this error while running your application on internal weblogic server delete the following file WLS_DIAGNOSTICS000000.DAT search the file in following path C:\jdev_work\system11.1.1.5.37.60.13\DefaultDomain this file is in DefaultDomain folder of your jdev. and delete the WLS_DIAGNOSTICS000000.DAT file . and run your applicatuon
1 comment
Read more

Overview Editor for bc4j.xcfg

By
This is used to customize the configuration settings for the application pool, connection pool, and transactions. Select the Application Module, then select a configuration from the Configurations list. You can specify a Default Configuration from the dropdown to use with selected application module. Edit the name of the configuration in Details. Its having 3 tabs 1.Database and Scalability 2. Properties 3. Custom Properties Database and Scalability Tab : In Database and Scalability you can mention the JDBC data source definition for each application module. You can choose to connect to a JDBC data source or to a JDBC URL.The default connection type is the default data source. A data source is a vendor-independent encapsulation of a database server connection on the application server. 1. Data sources ( JNDI name) offer advantages over a JDBC URL connection because the data source can be tuned, reconfigured, or remapped without changing the deployed application. 2. JDB...
4 comments
Read more

WebCenter Deployment Architecture

By
The main components of the deployment architecture are: • WebLogic Server • Portlets deployed in Portlet Container • Metadata storage for customization information • Enterprise Content Management solution with Content Adapters • WebCenter Services • WebCenter Search • Identity Management         WebLogic Server, which is a Java EE–compliant application server, is at the center of WebCenter. WebCenter applications are Java EE applications that are deployed to WebLogic Server. WebCenter Spaces is a prebuilt custom application using WebCenter Framework and Services. Portlets : WebCenter applications can consume portlets. Portlets are deployed into a Portlet Container and are accessed by various HTTP-based network protocols such as WSRP and SOAP. Oracle WebCenter supports several portlet APIs such as JSR 168 and PDK Java.   Metadata Services : WebCenter applications can be customized or personalize...
Post a Comment
Read more