I tried to set default value with <c:out> action. Ex) <c:out value="${customer.phoneHome}" default="XXXX"> notice: XXXX is a value contains multibyte characters. When I open web location, an error occurred. The error message is displayed as follows. ================================================== ??????? c ?????????????????? null: tag = 'out' / attribute = 'default': An error occurred while parsing custom action attribute "default" with value "??": Lexical error at line 1, column 1. Encountered: "\u306a" (12394), after : "" ================================================== I just noticed that the ELParser.jj has UNICODE_INPUT set to false (by default). The fix should be as simple as setting it to true and regenerating the parser.
Would it be possible for you to list the JSP code in which this is happening Tx.
I was able to reproduce this : Thanks, Prasad
Bug 9257 - ELParser doesn't parse non-ascii value As Kan suggested, I've added UNICODE_INPUT = true to the ELParser.jj options. This doesn't seem to have caused any regression in the existing command line parser tests. I also added a new command line parser test to try inputting a non-ascii string. I've confirmed that without the fix, the string causes an error, whereas with the fix, the string is processed correctly. So, this appears to be fixed. However, I don't have easy access to non-ascii pages so I haven't completely confirmed this fix in an actual JSP. I would appreciate it if someone would confirm this fix (Kan?)
I tried to do the existing command-line parser tests with the regenerated ELParser, so I have appreciated correctly. In this case, the tested non-ascii string is not "\u1111" but "\u30c6\u30b9 \u30c8". ( "\u1111" code isn't displayed fundamentally under Japanese environment. ) And I also have completely confirmed this fix in an actual JSP. Thanks, Kan Ogawa
Many Thanks!