What you're proposing sounds good to me (a complete novice, I must emphasise), but I think you hit the nail on the head there. Wicket is fantastic for the work I'm doing precisely because it /is/ stateful. I'd hate to see wicket going down the route of obsessing over the reduction of server-side state management, because it'd lose a lot of its appeal in the process.
I agree. So what I'm thinking of is - like stateless pages and url mounting is now - something optionally; people can decide for themselves if they want to go through the extra effort to do this, but by default the programming models stays as it is now. Eelco
