This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 93747 - I18N - calendar component does not have a lang property
Summary: I18N - calendar component does not have a lang property
Status: CLOSED WORKSFORME
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: Sun Solaris
: P3 blocker (vote)
Assignee: _ edwingo
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2007-01-31 23:22 UTC by bugbridge
Modified: 2007-08-14 18:06 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-01-31 23:22:09 UTC
Original status: 5-Cause Known; Suggested Status: NEW

Original Target Release: shortfin_dev; Suggested Target Milestone : 5.5


Original submitter: kfrank

Description:
from bugs filed on creator sdn page - separate channel from direct to bugtraq
so needs to be filed in bt.

from http://webbugs.sfbay/rt/incidentDisplay?incidentID=784369

A DESCRIPTION OF THE PROBLEM :
The calendar component use the language option of the computer on which the
server runs.
When I test my site on my computer, it's ok but when I deploy on a web hosting,
it's  in English, not in french.
I can't change the hosting website regional settings !
The calendar component should use a lang property.


REPRODUCIBILITY :
This bug can be reproduced always.


(company - Solutions Objet , email - xxx@xxxx

Evaluation:
Fix in future version. Use AJAX popup calendar as a workaround.

Evaluation (Entry 2):
Since Edwin is planning to rewrite the calendar component after fcs, this bug
can be fixed later but not for fcs release. I am lowering the priority as its
not that major issue.
Comment 1 Pegah Sarram 2007-05-02 02:30:32 UTC
This is a user error. The user must define the supported locales by the app in
the faces-config.xml file. If the locale identified in a request is not defined
in faces-config.xml, JSF defaults the locale to server JVM's default locale. 

The component behaves correctly and there is no need for a lang property.

Here is an example of what should go into the faces config file:
 <application>
        <locale-config>
          <default-locale>en</default-locale>
          <supported-locale>de</supported-locale>
          <supported-locale>fr</supported-locale>          
          <supported-locale>ja</supported-locale>
          <supported-locale>zh</supported-locale>
        </locale-config>
    </application>   

Note, if the user is using a Braveheart component (1.4 project), then s/he also
 needs to add an entry to web.xml file for the theme to use. Woodstock
components don't need that entry.

For example:

<context-param>
      <param-name>com.sun.webui.theme.SUPPORTED_LOCALES</param-name>
      <param-value>en,ja</param-value>
</context-param>

Please verify and close it.
Comment 2 Lark Fitzgerald 2007-08-14 18:06:49 UTC
Closing.