[
https://issues.apache.org/jira/browse/JEXL-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838567#comment-16838567
]
Jarek Jarcec Cecho commented on JEXL-299:
-----------------------------------------
That was really fast, thank you [~henrib]!
> Improve message error when method could not be found
> ----------------------------------------------------
>
> Key: JEXL-299
> URL: https://issues.apache.org/jira/browse/JEXL-299
> Project: Commons JEXL
> Issue Type: Improvement
> Affects Versions: 3.1
> Reporter: Jarek Jarcec Cecho
> Assignee: Henri Biestro
> Priority: Major
> Fix For: 3.2
>
>
> We incorporated JEXL into our product and it's working really well - thanks
> for all the hard work and effort that went into the project!
> One thing that that does stand out as a possible improvement is to increase
> the verbosity of the following message:
> {code}
> org.apache.commons.jexl3.JexlException$Method:
> com.streamsets.datacollector.antennadoctor.engine.AntennaDoctorEngine.evaluateCondition@1:48
> unsolvable function/method 'intersection'
> {code}
> It took us a few hours the first time we saw this exception as the
> {{intersection}} method definitely existed. It turned out that we were
> mistakenly calling it with an array rather than with expected list and thus
> method {{intersection(Object[]}} was indeed not found as only
> {{intersection(List)}} was present.
> Any chance to improve the error message and in addition to printing the
> missing method also print the argument which Jexl is trying to match? E.g.
> something like:
> {code}
> org.apache.commons.jexl3.JexlException$Method: unsolvable function/method
> 'intersection(Object[])'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
