[
https://issues.apache.org/jira/browse/JEXL-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154589#comment-14154589
]
Henri Biestro commented on JEXL-146:
------------------------------------
Committed a fix in the 3.0 trunk (unsolvable variable/property/method); let me
know if this is what you expected.
On the release subject, you should post/ask to the mailing list to see if any
committer is interested in releasing 3.0.
> 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
>
> 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)
