You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Henri Biestro (JIRA)" <ji...@apache.org> on 2015/03/19 16:24:38 UTC
[jira] [Resolved] (JEXL-146) Performance problem in
Interpreter.unknownVariable mechanism
[ https://issues.apache.org/jira/browse/JEXL-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Biestro resolved JEXL-146.
--------------------------------
Resolution: Fixed
> Performance problem in Interpreter.unknownVariable mechanism
> ------------------------------------------------------------
>
> Key: JEXL-146
> URL: https://issues.apache.org/jira/browse/JEXL-146
> Project: Commons JEXL
> Issue Type: Bug
> Affects Versions: 2.1.1, 3.0
> Reporter: David Maplesden
> Fix For: 3.0
>
>
> When JEXL is used in non-strict mode it silently ignores unknown variables. However it still constructs a {{JexlException.Variable}} exception, even though it doesn't throw it.
> Constructing exceptions in Java is expensive. If you happen to have a situation where unknown variables are common then this becomes a performance problem. It is showing up as an issue in our application.
> Inspecting the source of {{Interpreter}} it looks like a similar issue could also occur with a number of the other exceptions. They are always created, even if they are not going to be thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)