Original status: 5-Cause Known; Suggested Status: NEW

Original Target Release: mako_dev; Suggested Target Milestone : Dev

These items should be added to the Status Whiteboard: WAV_APPROVED

Original submitter: kfrank

Description:
6276130 was supposed to fix some runtime issues about certain components
not showing labels from localized files at runtime - and the fix
involved, besides creation of localized theme jars, that user needed
to do some additional steps anytime they wanted to run in another locale.
(see that bug or discuss with developers if you need details on the special steps)

Those steps were followed and the dropdown and listboxes, in both std and basic,
still did not show their labels like item1, item2. etc from localized files
at runtime.

I was asked that, instead of keeping 6276130 open in fixed failed state, to open
separate
bugs so am doing so; but there is nothing different in this issue that is not
mentioned in the last comment of 6276130.

Description (Entry 2):
Need to document this in the i18n tutorial.  It was suggested that a footnote be
added to both tutorials.

Description (Entry 3):
There is no data that our customers are hitting this issue. Please monitor the
chinese and japanese forum and add forum data on these issues and we will
reevalute this bug to be fixed in a patch.

Evaluation:
This bug does not include a description of how to reproduce the problem.

Evaluation (Entry 2):
Root cause is missing localized webui.jar in project class path. Fixed by IN 83747.

Evaluation (Entry 3):
There is an additional cause:

The labels in question (all "item" labels supplied by default to listbox, cb/rb
group, add/remove, and dropdown, and the default column labels in a table) are
fetched from a property bundle in the DefaultOption bean's constructor. After
deployment of an application, when a client request is received by the Faces
servlet, the first thing that the servlet does is restore the view. This
creates/recreates an instance of the page bean, and the page bean's constructor
is invoked. Since changes to the DefaultOptions bean are persisted in the page
bean constructor, a default options bean is created, and in its constructor it
attempts to fetch its labels from a property bundle. Message fetching is done
via the Braveheart utility class MessageUtil.

The problem is that the Faces servlet has not yet set the locale on the view
root, so when the MessageUtil class asks the faces context for the locale, null
is returned. It then falls back on the server's default locale, which is usually
English.

Possible fixes: modify bean to do lazy initialization when getter is called, or
modify locale lookup to check HttpServletRequest locale directly.

Evaluation (Entry 4):
Requesting waiver for Thresher.

This is a limited use-case. The default beans are meant only as suggested
values, they will not be used as is in real applications. This problem occurs
only when the beans are used without modifications. When the user modifies them,
to add data that makes sense for his application, the property settings will
always overwrite the default settings.