DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39193>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39193 Summary: [JEXL] Static method resolution and changes to context Product: Commons Version: 1.0 Final Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: JEXL AssignedTo: commons-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] From: Guido Anzuoni <[EMAIL PROTECTED]> 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. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
