Reviews and Ratings
I have been using bazaar for over a year now on my personal projects (over 10K lines of code) and it has been a pleasure all the way.
We have been using it now on our project at work for a few months and there have been no issues with adoption. We are using it in a centralised way to make everyone comfortable with it i.e. a better subversion.
Centralised or distributed whichever way I've wanted to use it bazaar has supported it. The eclipse plugin is pretty good - not quite as fancy as some other VCS plugins though.
The shared repository concept that bazaar has is really good. It saves us a lot of time when creating local branches as it does not have to pull down revisions that it already has. It is quite a simple concept which seems odd when you first encounter it but is a massive time saver in the long run.
Spring webflow is better than spring mvc in that it helps with state management, but like all things spring it places so much in xml and annotations that it becomes difficult to keep things sane.
Forget refactoring or anything like that with it.
If you are looking for a better Spring MVC then use Spring Webflow. If you are looking for better long term productivity look elsewhere.
Wicket is a framework based on what made Java great i.e. Java itself. There is no xml based configuration or plugging things together. The presentation markup is in plain html. Errors are very clear and helpful.
I feel confident when refactoring with Wicket (since it is plain Java). Java tooling is excellent whereas xml, bytecode injection, dynamic proxy/introspection etc. tooling is not.
Unit testing in Wicket is very simple and easy to do.
Wicket provides a way of managing state which to me is quite intuitive and easy to use (and again no xml!). This makes work flows really easy.
What's not so hot? Not as many polished components as other frameworks. Although I recently discovered wiquery which is integrating jquery with Wicket. I have yet to try this out so no comment on it. Not that Wicket prevents you from using things like YUI or other javascript libraries, it's just that they are not seemlessly integrated.
Wicket does feel quite abstracted from the techie web side of things which is both good and bad. It is good in the fact that I focus on developing business logic. The bad is when I've got to do something that is out of the ordinary and not straight forward to do in Wicket.
On the whole I found it very productive in building web sites using a TDD approach.