I'm not sure what you mean by "property accessor". The Tapestry community is just as tied down/used to using ognl expressions as much as any other. Tapestry-prop is a side project Howard created for very specific consulting engagements where the performance overhead of ognl was unacceptable for some clients.
I think it's a mistake to throw ognl out at this point. The expression language is awesome, it just needs a performance boost. (it's also been out and about being used for years) Chris Brock wrote: > > I think the problem is that the Tapestry solution is simply a property > accessor package, which doesn't really meet the needs of the established > WebWork community which relies on "expressions" in addition to properties > to accomplish tasks. > > That being said, my project (MVEL) stands willing to step in and assist. > I think it's performance and flexibility speak for itself: > http://wiki.mvflex.org/index.php?title=MVFLEX_Expression_Language > -- View this message in context: http://www.nabble.com/OGNL-performance-detrimental-to-Struts-2-tf2804655.html#a7940406 Sent from the Struts - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
