Hi, I am a newbie in Tapestry. Our organization is going to build a large scale web application in 3 months time and me together with 2 other developers have been asked to research and come up with a good web framework to use. I suggested Tapestry but almost all the developers on our team rejected it outright with reasons such as incompatibility issues with any major Tapestry release, very bad documentation and no professionally written books on tapestry. I googled and also learnt there is Tapestry 6 in the works which would also be a whole new beast not compatible with all previous Tapestry versions. Why this at all? I also hear Tapestry 5 has it's own built-in IoC container. Is this necessary for a webframework? Isn't it an overkill, or in otherwords an over engineered piece of software? I learnt Wicket is an excellent web framework with a very good support plus an active mailing list. From the way I'm seeing things, my team is gradually leaning towards Wicket. Can someone here offer me an unbiased comparison of Tapestry and Wicket I may use to change my team's mind?
Thanks, Rob
