My understanding is that tap4, internally, uses ognl much less than before. In terms of binding properties, since tap4 lets you develop custom binding mechanisms, you could always write your own replacement and plug it in. But then, Howard's already done that. :) Take a look at http://howardlewisship.com/tapestry-javaforge/tapestry-prop/ It won't replace complex ognl expressions (things like: ognl:someList.{? bar=="baz"}, for instance), but it will do just fine for replacing simple property paths (foo.bar.baz) and is more performant than ognl.
Robert > Hi there -- > > I saw this post > (http://www.theserverside.com/news/thread.tss?thread_id=41923) > over on theserverside. It was announcing Stripes 1.4. The original post > and > comments are all refering to what a dog ognl is from a performance > perspective. > > > So I got to ask the question is Tapestry going to chuck ognl as well? > > -Pat > > --------------------------------------------------------------------- > 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]
