Javalobby - Comments for "Interview: How Wicket Does Ajax"

I added a list of useful

geertjan — Sun, 27 Apr 2008 18:43:08 -0400

I added a list of useful resources to the end of the interview. Especially the first, to the list of Ajax/Wicket samples, is extremely helpful.

Wow - fabulous interview,

eldaaran — Sun, 27 Apr 2008 00:25:31 -0400

Wow - fabulous interview, gentlemen! I've been doing a lot of reading in this area lately trying to decide which framework to do my next project in - and after seeing your examples and hearing your thoughts on the design, I'm very excited to try some of this out.

Thanks for taking the time!

Wicket has been a consistent

d3ik — Sat, 26 Apr 2008 23:00:31 -0400

Wicket has been a consistent performer for me. Both in terms of developer productivity and extensibility.

The ajax support works very well. The issue I have run into on previous (pre-Wicket) projects has always been unobtrusive javascript. I'd always find myself building the functionality twice; the first layer being just the basic webapp that works if javascript is turned off, then an 'enhanced' javascript layer on the client that interacts with a server side API.

Wicket handles this very well with the component model. Every component knows how to render itself, so I just have to worry about updating that component tree and flagging components that I'd like to be redrawn on the client. This allows me to handle the logic of the event without getting bogged down in low levels of the HTTP exchange for every form submit or link click.