This commit enhances FunctionReference to also support MethodExecutor instances for evaluation (besides static java.lang.reflect.Method instances). This enables dynamic SpEL function definitions where the function to be executed is not known at compile time.
Additionally this commit - removes all mentions of lambda function definitions in comments since they are not implemented - fixes the type name in the message of the thrown SpelEvaluationException in case the value of the function has the wrong type and cannot be executed
Issue SPR-10589
Comment From: obecker
I have signed and agree to the terms of the SpringSource Individual Contributor License Agreement.
Comment From: obecker
It would be great if this change could be accepted for the 3.2 branch so I could use it on my current projects. However, since this is an enhancement, the corresponding documentation should probably extended as well (unless it becomes an undocumented feature in version 3.2 ...) The relevant chapter is http://static.springsource.org/spring/docs/3.2.x/spring-framework-reference/html/expressions.html#expressions-ref-functions
Comment From: pivotal-cla
@obecker Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-cla
@obecker Thank you for signing the Contributor License Agreement!
Comment From: rstoyanchev
Closing as outdated, along with related issue. The Javadoc issue seems to have been cleaned up since.