[ 
https://issues.apache.org/jira/browse/WW-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366105#comment-16366105
 ] 

Aleksandr Mashchenko edited comment on WW-4919 at 2/15/18 6:57 PM:
-------------------------------------------------------------------

Just found out there is a catch. {{java.lang.IllegalArgumentException: 
Malformed \uxxxx encoding}} will be thrown only if there is no fallback / 
default properties file w/o malformed encoding.

And it id caused by not a original exception, that is why it is ignored in 
Struts.


was (Author: aleksandr-m):
Just found out there is a catch. \{{java.lang.IllegalArgumentException: 
Malformed \uxxxx encoding}} will be thrown only if there is no fallback / 
default properties file w/o malformed encoding.

> The load of properties file doesnt show the Exception obtained if exist a 
> problem with Unicode character
> --------------------------------------------------------------------------------------------------------
>
>                 Key: WW-4919
>                 URL: https://issues.apache.org/jira/browse/WW-4919
>             Project: Struts 2
>          Issue Type: Improvement
>         Environment: When loading Struts2 in the Web Application
>            Reporter: Manuel Villalobos
>            Priority: Minor
>             Fix For: 2.6
>
>
> When loading a properties file for use with the Text tag or with getText 
> inside the Action, if a Unicode character has a problem the total content of 
> the file is not loaded and they are not available for use. The problem is 
> that the error found in the load is nowhere seen.
> Please help her in situations like that show up in the load the error you get.
> When trying to load manually the properties Java file throws the message 
> "java.lang.IllegalArgumentException: Malformed \ uxxxx encoding"
> Please help you so that when there are problems loading the properties file, 
> messages will be generated in the log



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to