Originally posted by Rogerio Kioshi:
Hi,
Wicket is a new framework for me.
Has this framework been adopted by many companies around the world?
What should I tell my customers as good reasons to convince them Wicket is more indicated that other frameworks?
Thank you
Wicket is quite popular. The
mailing list for instance has topped the Ruby On Rails list on most other web frameworks.
The people who work on Wicket use it for their projects as well, and that includes companies like
Teachscape, and
Servoy.
Now, personally I think that popularity shouldn't determine the choices you make for frameworks. Especially in the
Java world, there are plenty of examples around where that turned out badly (think
EJB 2 and
Struts for instance). As reasons why Wicket might be a good framework for you... it depends on what you need. Wicket is an excellent choice when you need to create relatively complex (web) user interfaces, and/ or you need to scale the development effort to larger teams, and/ or maintainability is important (which I'd argue always is the case for anything but the most trivial projects).
But read the first sections of chapter one of
Wicket In Action, which can be downloaded for free.