Kent Tong wrote:
Ron Piterman <rpiterman <at> gmx.net> writes:
Bad me, I didn't read the whole thread -
my two cents: I would find it better to combine both, so one *may* use
annotations, or one *may* implement an interface, which gives you a
strong compile-time check...
By method naming, Howard means just method naming *without* implementing
any interface.
yes I know, but it skips my mind why do such a thing - if the methods
are predefined, why not create an interface for them? is there a solid
reason?
though using tapestry for quite a while I don't remember tapestry event
method names - should I?
when I implement a listener (for a page event), I add the implemenets
clause, navigate in the IDE to the interface (eclipse F3) and copy the
method into my class.
I think howard is considering taking into the pages/component classes a
concept that is very fruitfull in the IoC, but is contraproductive for
this usecase.
Cheers,
Ron
--
Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
