[
https://issues.apache.org/jira/browse/JEXL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
peter royal resolved JEXL-28.
-----------------------------
Resolution: Won't Fix
Fix Version/s: 1.1.1
You can use your own Uberspect in JEXL-13 to achieve this.
> Enhance the resolution of properties and methods
> ------------------------------------------------
>
> Key: JEXL-28
> URL: https://issues.apache.org/jira/browse/JEXL-28
> Project: Commons JEXL
> Issue Type: Improvement
> Affects Versions: 1.1
> Reporter: Weikuo Liaw
> Priority: Critical
> Fix For: 1.1.1
>
>
> JexlContext need provide additional methods, such as
> 1) Object getProperty(Object object, String propName);
> 2) void setProperty(Object object, String propName, Object propValue);
> 3) Object invokeMethod(Object object, String methodName, Object[] params);
> where object can be null for the non-object properties/methods.
> ASTIdentifier, ASTArrayAccess, ASTAssignment, and ASTMethod can use them for
> unresolvable properties/methods.
> This is similar to what are changed by myFacese over commons EL to support
> friendly VariableResolver and PropertyResolver for applications.
> I use "ObjectinvokeMethod()" instead of "Method getMethod(object,
> methodNae)", because a method may not be implemented as a java method. Such
> as in commons validator, validators are registered in the configuration file
> of validation forms.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
