Wicket isn't suitable for highly scalable or single page applications as is (the ones which benefit from a rich client side and a stateless API approach). It is

Wicket isn't suitable for highly scalable or single page applications as is (the ones which benefit from a rich client side and a stateless API approach). It is highly productive for typical backoffice applications though. The only problem is the complexity of the framework - writing custom reusable components is really hard.