[ https://issues.apache.org/jira/browse/JEXL-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732557#action_12732557 ]
Henri Biestro edited comment on JEXL-3 at 7/17/09 7:54 AM: ----------------------------------------------------------- Static method resolution is fixed in 2.0. was (Author: henrib): Fixed in 2.0. > [JEXL] Static method resolution and changes to context > ------------------------------------------------------ > > Key: JEXL-3 > URL: https://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 <ganzu...@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. - You can reply to this email to add a comment to the issue online.