Wow, that was a long mail. It's a bit unfortunate that many of the abstractions in Wicket actually came from the idea of separating the servlet and portlet environments, and that we won't need those now, but I guess that's the way it goes. Most of those abstractions proved to be useful anyway.
I think I agree with the proposal for the large part. For the details, I think it is better to discuss actual code. The goal you are setting seems to be high, but if you can pull it off, it sounds excellent! One thing about the implementation you're working on. Do you think you can provide a test project with a configured portlet environment (e.g. based on JetSpeed) so that it is real easy for people (including the other team members of Wicket) to check it out and let our debuggers loose on it? For me, and at least a couple of others, the fact that it is quite some work to set a portlet server up, configure it to run a (Wicket) application etc has been the greatest stumbling block in trying to help out and review. If you can provide an environment that is really easy to set up, I bet there will be quite a bit of interest and it would increase the changes of succes this time considerably. Cheers, Eelco
