I've long since abandonned JSF in favor of Wicket to build what you call in-house apps: the latter being much more designer-and-developer-friendly imho. But I w

I've long since abandonned JSF in favor of Wicket to build what you call in-house apps: the latter being much more designer-and-developer-friendly imho. But I wouldn't use Wicket (nor JSF for that matter) for a public facing site, because it relies too much on the session. It is possible to produce stateless pages in Wicket but it's not worth the hassle. For such a use case, I would rather use a classic MVC-style framework. Something à la Stripes or Spring MVC, although I am not very happy with the prospect of using JSP (or Freemarker or Velocity) as the view layer. I'm also experimenting with using JAX-RS, coupled with a templating library as a web framework. Didn't push the experiment too far though, but it's clear that it's a barebone solution compared to classic web frameworks.