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

Passivation and Activation in ADF (Application Module )

By
1. For performance reasons, ADF keeps a pool of application modules in memory. It tries to give each session the same application module as the session used during the last request; however, this might not be possible during peak load of your application. 2. In this case, ADF saves the application modules state in a database table so the application module can be used by another session. This is called passivation . 3. When the first session needs the application module again, its state is retrieved from the database process known as activation . 4. If you have made an error in your code and depend on some variable that is not persisted correctly when your application module state is stored, you will experience mysterious errors under high load.   Enable/Disable Application Module Pooling : Right-click on your application module, choose Configurations.By default, each application module has two configurations. Ensure that the one ending in …Local is selected and then click
1 comment
Read more

Get modified rows from Entitiy Cache

By
To get the modified rows from entity cache we have getEntityState() method at EntityImpl class. Refer to my previous blog  Accessing EO impl methods from VO impl  where i am overriding the getEntityState() in EOimpl and calling it in VOImpl. We can use methods written or overridden in VOImpl class to AMImpl class. There are different states associated with an entity object. STATUS_UNMODIFIED STATUS_MODIFIED STATUS_NEW STATUS_DELETED STATUS_DEAD We have to check the state or row in our AmImpl class by using the VOImpl method and through this we can distinguish the rows present at vo. Add below code in AMImpl class along with my previous post. public void geCachedRowsCount(){         JobsVOImpl jobsVo = (JobsVOImpl)this.getJobsVO();         RowSetIterator iter = jobsVo.createRowSetIterator(null);             while(iter.hasNext()){             Row row = iter.next();             byte state = jobsVo.getEntityState(row);             System.out.println("Job_id -&
2 comments
Read more

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