[ 
https://issues.apache.org/jira/browse/JEXL-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Biestro resolved JEXL-83.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Later)
                   2.0.2

Added JexlThreadedArithmetic that allows different threads to manipulate the 
arithmetic leniency per thread.

Committed revision 1072000.
M       src/test/java/org/apache/commons/jexl2/CacheTest.java
M       src/test/java/org/apache/commons/jexl2/PublicFieldsTest.java
M       src/test/java/org/apache/commons/jexl2/UnifiedJEXLTest.java
M       src/test/java/org/apache/commons/jexl2/junit/Asserter.java
M       src/test/java/org/apache/commons/jexl2/IssuesTest.java
M       src/test/java/org/apache/commons/jexl2/AssignTest.java
M       src/test/java/org/apache/commons/jexl2/ArithmeticTest.java
M       src/test/java/org/apache/commons/jexl2/JexlTestCase.java
M       src/test/java/org/apache/commons/jexl2/IfTest.java
M       src/main/java/org/apache/commons/jexl2/JexlArithmetic.java
A       src/main/java/org/apache/commons/jexl2/JexlThreadedArithmetic.java
M       src/main/java/org/apache/commons/jexl2/JexlEngine.java
M       src/site/xdoc/changes.xml


> Make JexlArithmetic immutable (and threadsafe)
> ----------------------------------------------
>
>                 Key: JEXL-83
>                 URL: https://issues.apache.org/jira/browse/JEXL-83
>             Project: Commons JEXL
>          Issue Type: Improvement
>            Reporter: Sebb
>            Assignee: Henri Biestro
>             Fix For: 2.0.2
>
>         Attachments: JEXL-83.patch
>
>
> The JexlArithmetic class is currently not thread-safe because of the single 
> field:
>     /** Whether this JexlArithmetic instance behaves in strict or lenient 
> mode. */
>     protected boolean strict;
> If this field were made final, and the setLenient() method removed, then the 
> class would be immutable and therefore thread-safe.
> This would mean that JexlEngine would also have to change.
> The class is new to 2.0, so this is the best time to fix this.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to