[ 
https://issues.apache.org/jira/browse/TAPESTRY-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578650#action_12578650
 ] 

patklein edited comment on TAPESTRY-1765 at 3/14/08 1:38 AM:
------------------------------------------------------------------

darn... the attached unit test is not working as intended, it actually says ok 
to the old version as well (just rechecked) :|
I guess something there is behaving differently as in a tomcat environment

      was (Author: patklein):
    darn... the attached unit test is not working as intended, it actually says 
ok to the old version as well (just rechecked) :|
  
> getting language independent messages fails
> -------------------------------------------
>
>                 Key: TAPESTRY-1765
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1765
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 4.1.3
>         Environment: WinXP SP2, Java 1.5.0_11, Tapestry 4.1.3, Hivemind 1.1.1
>            Reporter: Christian Nutz
>             Fix For: 4.1.6
>
>         Attachments: org.apache.tapestry.junit.MockPage1.properties.patch, 
> org.apache.tapestry.junit.MockPage1_en.properties.patch, 
> org.apache.tapestry.junit.TestComponentMessages.java.patch, 
> org.apache.tapestry.servies.impl.ComponentMessagesSourceImpl.java.patch
>
>
> When I call getMessages().getMessage() in a page with a message key, which 
> only exists in the default properties file (app.properties, and not in 
> app_de.properties for example), no message is being returned, but only the 
> key "[MESSAGE_KEY]". Before the update from Tapestry 4.1.2 to 4.1.3, this 
> problem did not occured.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to