One possible way to resolve the issue: if the DTD used is earlier than 4.0, then use the 'ognl' prefix as a default for 'binding'. Otherwise default to the one that the component provides.
----- Original Message ----- From: "Howard Lewis Ship" <[EMAIL PROTECTED]> To: "Tapestry users" <[email protected]> Sent: Tuesday, May 10, 2005 7:40 PM Subject: Re: 4.0: listeners On 5/10/05, Konstantin Iignatyev <[EMAIL PROTECTED]> wrote: > Then I would say that compatibility with 3.0 is unnecessary broken. It > is very easy to put something like this inside of T4 No, backards compatibility is NOT broken. The syntax ognl:listeners.method is what a 3.0 app would use, and that still works. For 4.0, there's the listener: prefix, so listener:method is equivalent. Since the listener parameter specifies "listener" as its default prefix, you can just specify the method name, "method". Again, all of the following are equivalent (for the Form's or DirectLink's listener parameter): ognl:listeners.myMethod listener:myMethod myMethod I prefer the last version. The latter two are marginally more efficient than the OGNL version (though invoking a listener method does use some amount of reflection). -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- 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]
