This is a _great_ idea! My only concern with this would be how much of an overhead this conversion might be. Then again, we cache String -> TreeNode conversion that Ognl does, so we could just turn that cache in to String -> String -> TreeNode I suppose.
Converting .. to [1] is easy enough, but what about "/"? Our converter would need to be smart about foo/bar vs 10/5... or would we just not care about mathematic operations? Converting "." to "peek()" is also tough, since we don't want "foo.bar" to become "foopeek()bar". The preprocessor needs to be simple and fast, otherwise we'll end up writing our own parser! -Pat ----- Original Message ----- From: "Erik Beeson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 23, 2003 11:22 AM Subject: RE: [OS-webwork] Ognl: peek(), up(), and down() > Could we write a small preprocessor that would just convert "../blah" to > "[1].blah" before handing it off to Ognl? Would it help the situation if > we removed a means of moving up and down in the stack like in Velocity? > > --Erik > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
