You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Rahul Akolkar (JIRA)" <ji...@apache.org> on 2006/08/09 06:47:14 UTC
[jira] Updated: (JEXL-3) [JEXL] Static method resolution and
changes to context
[ http://issues.apache.org/jira/browse/JEXL-3?page=all ]
Rahul Akolkar updated JEXL-3:
-----------------------------
Bugzilla Id: (was: 39193)
Fix Version/s: 2.0
I agree that the VariableResolver style API is much better than get/set vars. This has to be moved to a major release (if this change is to be made). Therefore, updating fix version to 2.0.
> [JEXL] Static method resolution and changes to context
> ------------------------------------------------------
>
> Key: JEXL-3
> URL: http://issues.apache.org/jira/browse/JEXL-3
> Project: Commons JEXL
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Operating System: other
> Platform: Other
> Reporter: dion gillard
> Fix For: 2.0
>
> Attachments: jexl-patch.zip
>
>
> From: Guido Anzuoni <ga...@gmail.com>
> Here I will try to explain may changes to see if you agree to include in the trunk.
> 1. UberspectImpl
> I need to include static methods resolution in expressions (e.g.
> System.currentTimeMillis()). I patched the class to allow it.
> 2. JexlContext
> Resolving vars using a Map is not enough flexible for my needs. I have modified
> it to have a single method
> public Object resolveVariable(String var);
> This allows me for better flexibility in the resolution process.
> I have implemented a JextContext based on a java.util.Map, an extensible
> JexlContext and a delegating JexlContext.
> The extensible resolver is abstract and has a "parent" context to which
> delegates in the case local resolution failes.
> Delegating implementation extends the extensible context and uses another
> JexlContext for local resolution.
> More, I have removed any reference to JexlContex.getVars() in the code.
> If you wish I can send the modified classes to better evaluate my changes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org