[ 
https://issues.apache.org/jira/browse/TRINIDAD-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621454#action_12621454
 ] 

Matthias Weßendorf commented on TRINIDAD-65:
--------------------------------------------

I cleared all my browser cache in FF2 (IE is worse than FF, in terms of cache)
I compiled our 1.2.9.1 branch w/ JAVA 6
deployed the demo in Tomcat (running on JAVA6) => fine
fine means: I tried your test-case. I entered "foo" and clicked a command 
button. I saw no JS error and the message was shown.
set JAVA_HOME = ...\java5
started tomcat again (now running on JAVA5) => fine (same meaning as before)

both "tests" were done with the previously built Trinidad Demo (using Java6).

> The JS e.getFacesMessage method does not work when trinidad was compiled with 
> Java 6 (JSLocaleElementsGenerator does not work with Java6)
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-65
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-65
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.0.0-incubating-plugins, 1.0.0-incubating-core, 
> 1.0.1-plugins
>         Environment: Windows XP, Java 6
>            Reporter: David Übelacker
>            Assignee: Matthias Weßendorf
>             Fix For: 1.0.9-core, 1.2.9-core
>
>         Attachments: JSLocaleElementsGenerator.patch, LocaleDataResolver.java
>
>
> If trinidad was compiled with Java 6, you get the JS error "e.getFacesMessage 
> is no Function".
> The reason for this problem is, that the JSLocaleElementsGenerator  of the 
> maven-i18n-plugin does not work with Java 6.
> The JSLocaleElementsGenerator  uses some java resource bundles to generate 
> the LocaleElements files. These resource bundles are part of the rt.jar file 
> until java 5. With java 6 these bundles doesn't exist anymore, are hard coded 
> and can be accessed     through sun.util.resources.LocaleData (not on the 
> public API).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to