It may never be; the design of T5 allows for easy property expressions right in the binding, and more complex expression delegate out to Java code easily (this is practical in T5 because of the automatic class reloading).
A lot of the "magic" logic in BeanEditForm and Grid is based on some APIs that OGNL will have trouble replicating ... in terms of identifying a property is a type-safe manner, and gaining access to annotations on the getter and/or setter. On 3/6/07, Jiri Mares <[EMAIL PROTECTED]> wrote:
Hi Howard, > 2) OGNL isn't supported in T5. OGNL won't be supported or not yet. -- Jiří Mareš (mailto:[EMAIL PROTECTED]) ČSAD SVT Praha, s.r.o. (http://www.svt.cz) Czech Republic --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
