[
https://issues.apache.org/jira/browse/JEXL-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro resolved JEXL-99.
-------------------------------
Resolution: Fixed
Updated javadoc and example.
Committed revision 927136.
xdocs/reference/examples.xml
src/main/java/org/apache/commons/jexl2/JexlEngine.java
> Documentation of Thread Safety / Invalid code examples on homepage
> ------------------------------------------------------------------
>
> Key: JEXL-99
> URL: https://issues.apache.org/jira/browse/JEXL-99
> Project: Commons JEXL
> Issue Type: Task
> Affects Versions: 2.0
> Reporter: Marcel Schoen
> Assignee: Henri Biestro
> Priority: Minor
> Fix For: 2.0.1
>
>
> I had trouble with a custom method invoked in a JEXL script. This method
> throws a RuntimeException, which got swallowed with JEXL 2. Using the
> debugger, I found the "strict" flag of the Interpreter to be false, even
> though I had invoked "JexlEngine.setLenient(false)" in my initialization code.
> Now I suspect my initialization logic to be faulty, but while I looked into
> this, I realized that the javadoc of JexlEngine doesn't really tell me if I
> can use it as a singleton or not (or if I should, for that matter). If so,
> are its various methods thread-safe or not? It only says so for a few methods
> like "setDebug()".
> In addition, some code examples on the homepage are heavily outdated. For
> example, the first code fragment on this page
> http://commons.apache.org/jexl/reference/examples.html
> shows the usage of a class "ExpressionFactory" which doesn't even exist in
> the JEXL 2 source tree. Of course it would be nice if these examples would
> show how to correctly use "JexlEngine", for instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
