So I was reading another question under the Wicket tag comparing Apache Wicket and Apache Click. A concise explanation, in my opinion. I am more familiar with the Wicket world t
Wicket is stateless by default, and switches into stateful mode when it needs to. It is very easy to break the stateless mode.
I've found it useful to annotate intended stateless pages and stateless components with @StatelessComponent
, which is found in the wicket-devutils project. I then add
a StatelessChecker
in my WebApplication.init()
method like this:
protected void init(){
...
this.addPostComponentOnBeforeRenderListener(new StatelessChecker());
...
}
This way I always get an exception about the offending stateful component.