This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information

--Record translation

Documents for the development of and with JVx.

--Record translation

Postby Development@SIB » Mon Oct 05, 2015 5:06 pm

This article is outdated - please use our new system at

Sometimes it's important to translate records of a table/data book. If you have such a requirement, you can use different solutions:

  • Use a view and translate column values via database
  • Translate values on the client (without database)

If you choose the first option, everything will be fine because it'll be possible to use filtering and searching via database. With second option, only client-side filtering and searching will work. Why?

If you translate e.g. an English content to German on client side, the value in the database is still English. If the user tries to search a German value, the database won't find it because all values are in English.

The second option is easier to use and the first one needs some database/view logic. The second option will load/fetch all records because of sorting and filtering. If you have only few records, or searching and filtering is not important, the second option will be perfect.

How client translation works?

StringDataType has following methods:

Code: Select all
public setTranslator(ITranslator pTranslator)
public ITranslator getTranslator()

If you set the translator for a column with a StringDataType, every value will be translated automatically. The data type has the method:

Code: Select all
public Object prepareValue(Object pObject)

which is responsible for the translation.

What is an ITranslator?

We have default implementations for the interface. Simply use a TranslationMap, an UIComponent or an instance of IControl. Usually it's not needed to implement your own translator.


The UIEnumCellEditor automatically translates the display values. Simply check the source code or use following snippet:
Syntax: [ Download ] [ Hide ]
StringDataType sdtName =  new StringDataType();

MemDataBook mdbData = new MemDataBook();
mdbData.getRowDefinition().addColumnDefinition(new ColumnDefinition("SYSTEMNAME"));
mdbData.getRowDefinition().addColumnDefinition(new ColumnDefinition("NAME", stdName));
mdbData.getRowDefinition().addColumnDefinition(new ColumnDefinition("NAME_INTERN"));

//also possible
StringDataType sdtSysName =  (StringDataType)mdbData.getRowDefinition()
User avatar
Posts: 323
Joined: Mon Sep 28, 2009 1:54 pm

Return to Documentation