We (Johan and me) actually discussed this with Jonathan right after we
became active. Jonathan's reason was that he thought it was just
simpler/ more straightforward. On top of that, it saves a little bit
of memory.
Imho, I could live with both, but my preference now would be to keep
what we have
wicket uses callback methods instead of listeners for a simple reason: it is
a smaller memory footprint - there is no list to store, no listener
implementations to serialize. it is further my experience that you very very
rarely need more then one listener, so it cannot justify the overhead imho.
When I've started using Wicket few months ago, I found myself wondering: why
do I have to override methods instead add listeners to my component?
Developing forms is quite strange to me, when I have to override the
onSubmit() method. If we say "Swing-like OO Component Model", why there's no
liste
