JEXL developers - Any objections to me adding myself to the JEXL component?
I will be starting small -- fixing typos and broken/obsolete links and republishing the website etc. Over time, I'm looking at adding to the JexlContexts and JexlExprResolvers. For example, some ideas include: * A "TreeJexlContext", which is backed by a tree of contexts, where one may point to a current context node and variable resolution bubbles up to the root until the variable is found (or fails at root). * A "ScopedJexlContext", to support multiple scopes/contexts, allowing differentiation of the type context1.foo and context2.foo * An "ImplicitObjectsJexlContext", where contexts may be populated with implicit objects for a particular environment that aren't lost on JexlContext#setVars(Map) -- potentially handled by having a decorated JexlExprResolver instead. As a sidebar, Commons SCXML now supports using JEXL expressions in SCXML documents [1]. I have use cases similar to the suggestions above and some other usecases may potentially pop up as I think some more about this. -Rahul [1] http://svn.apache.org/viewcvs.cgi?rev=367112&view=rev --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
