Well, I used ANTLR because I'm familiar with LALR(1) parsers, and I knew I could make it work. Also, I don't think (from a quick look at the documentation) that you can do the Foo[] syntax (which I use to drop in the index count of the current indexed property) using OGNL. On the other hand, I'm not at all wedded to ANTLR, if someone wants to take a shot at implementing the grammer using another tool, that's great.
On a side note, one of the things I'm unhappy with is that I have to use AND and OR rather than && and ||, because when I used &&, it blows up the XML parsing of validation.xml. Is there a way to get around this? James > -----Original Message----- > From: Erik Hatcher [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 01, 2003 3:10 PM > To: Struts Developers List > Subject: Re: Validwhen returns, need some pixie dust on the > nightly build machine > > > Could we revisit why OGNL was not used for this? > > Both WebWork2 and Tapestry use OGNL extensively. OGNL is extremely > powerful and practically a defacto expression language these days. > > Erik > > On Tuesday, July 1, 2003, at 01:54 PM, James Turner wrote: > > Ok, now that the dust is settling on 1.1, I've re-checked-in the > > validwhen validator, but in order for the nightlies not to > break, the > > antlr.jar file (available from > http://www.antlr.org/download/) > needs > > to be put on the > build machine and the antlr.jar property in > > build.properties needs to point to it. > > > > James > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
