[
https://issues.apache.org/jira/browse/JEXL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro resolved JEXL-100.
--------------------------------
Resolution: Fixed
New Revision: 928405
URL: http://svn.apache.org/viewvc?rev=928405&view=rev
Log:
Updated Parser.jjt to define all acceptable tokens resulting in cleaner lexer.
Added 'register' syntax (#0-9) used by JexlEngine.{s,g}etProperty: syntax only
valid through ALLOW_REGISTER flag and REGISTERS lexical state.
Completed literal handling (array, integer, string, float).
Added:
commons/proper/jexl/trunk/src/main/java/org/apache/commons/jexl2/parser/ASTArrayLiteral.java
(with props)
commons/proper/jexl/trunk/src/main/java/org/apache/commons/jexl2/parser/ASTFloatLiteral.java
(with props)
Modified:
commons/proper/jexl/trunk/src/main/java/org/apache/commons/jexl2/Interpreter.java
commons/proper/jexl/trunk/src/main/java/org/apache/commons/jexl2/JexlArithmetic.java
commons/proper/jexl/trunk/src/main/java/org/apache/commons/jexl2/JexlEngine.java
commons/proper/jexl/trunk/src/main/java/org/apache/commons/jexl2/parser/ASTIntegerLiteral.java
commons/proper/jexl/trunk/src/main/java/org/apache/commons/jexl2/parser/ASTStringLiteral.java
commons/proper/jexl/trunk/src/main/java/org/apache/commons/jexl2/parser/Parser.jjt
commons/proper/jexl/trunk/src/test/java/org/apache/commons/jexl2/JexlTestCase.java
> Array access expressions fail when evaluated twice and cache is enabled
> -----------------------------------------------------------------------
>
> Key: JEXL-100
> URL: https://issues.apache.org/jira/browse/JEXL-100
> Project: Commons JEXL
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Henri Biestro
> Assignee: Henri Biestro
> Priority: Blocker
> Fix For: 2.0.1
>
>
> When caching is enabled, a cached array expression using an integer literal
> will fail at evaluation, the integer literal throwing an exception trying to
> coerce a ListGetExecutor to Integer.
> Sole workaround is to disable cache entirely which is not always possible;
> critical!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
