Note that there are some explanatory texts on larger screens.

plurals
  1. POInternalization of JSF project on WebSphere 7
    primarykey
    data
    text
    <p>I'm trying to implement loading Resource Bundles for JSF application from DB, following the sample: <a href="https://stackoverflow.com/questions/4499732/design-question-regarding-java-ee-entity-with-multiple-language-support">internationalization in JSF with ResourceBundle entries which are loaded from database</a></p> <p>For the test I coded getItSomehow() just as create HashMap and fill it with key "hello_world" and value "["+locale+"]"+"hello world"</p> <p>The sample works fine when I deploy it on Glassfish3. But when I use WebSphere AS 7, the jsf page is displayed correctly only for the first time. Opening the jsf page in other browsers (with other prefered language selected) I receive the respond always in the locale of first run. </p> <p>While debugging, I found the difference in implementation of ResourceBundle.java: Glassfish uses this class provided in rt.jar of the JDK1.6; but WebSphere has this class inside java.util.jar</p> <p>The ResourceBundle (of WebSphere) called from ApplicationResourceBundle.getResourceBundle() calls handleGetBundle() and finally invokes my.i18n.DbResourceBundle$DBControl.newBundle() . Called second (and further) time with different locale it doesn't invoke my override but just returns the same bundle created for first locale. </p> <p>The question: is it possible to code internalizable jsf web-application deployed on WebSphere AS 7.0.07, not digging nor hacking into internals of the AS? </p> <p>(environment: Windows XP, WebSphere AS 7.0.0.7, jdk1.6.0_24, jsf 2.1.4)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload