Yes, I assume you could do that as well, though I think that would be pretty confusing, since expressions in view layers (JSP, velocity) tend to be static in nature, so I doubt "[someInt].someVal" would ever crop up.
As for using the other expression language, yes, Ognl supports any kind of expression tree (Node interface), but that would be a lot of work to implement the WW EL in to Ognl's form. An easier way (and this will be included for backwards compatibility) would be to just include the old ValueStack code as well. However, by using Ognl we gain not having to maintian our own EL and a whole bunch of speed, as well as more powerful features (Ognl can even do lamba expressions). The only cost is switching your brain to use "." instead of "/" and "[1]" instead of "../". -Pat ----- Original Message ----- From: "boxed" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, December 29, 2002 12:30 PM Subject: Re: [OS-webwork] Ognl as replacement for WW EL > > "[1].name" -- "../name" > > does this mean you can do [someInt].name? In any case I find the WW EL > syntax clearer. Is it possible to plug in a different parser to OGNL that > takes WW syntax instead? > > Anders Hovmöller > [EMAIL PROTECTED] http://boxed.killingar.net > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
