How does Stripes compare with Wicket?

How does Stripes compare with Wicket in terms of ease of use, architectural principles, learning curve, maintainability, etc?

Originally posted by arulk pillai:
How does Stripes compare with Wicket in terms of ease of use, architectural principles, learning curve, maintainability, etc?

Stripes is an action-based framework, while Wicket is a component-based framework, which makes them fundamentally and architecturally different.

That said, they do have some similarities: very little XML configuration required, not full-stack but easy integration with other frameworks.

Stripes is probably easier to learn if you are already familiar with Struts or another action-based framework, while Wicket is closer to a Swing type of application.

In terms of maintainability, Stripes is excellent in my opinion because you do not need to constantly keep maintaining configuration files. How the code is connected to other parts is clearly indicated right there in the source, and that saves you loads of time when working on a large project with many developers.