I don't have time to go into a ton of detail right now (although I will try to do so later), but I went through the same evaluation process, although I compared every viable j2ee framework and eventually settled on Tapestry. Despite some hiccups, I still think it was the right decision.
The one caveat - I didn't have to spend nearly as much time trying to figure out HOW to do something in struts. The Tapestry learning curve and lack of documentation is definitely something that you have to take into account when choosing a framework. It will definitely slow you down until your team is up to speed. That said, it is a lot easier to reuse large amounts of code in Tapestry, by writing components, so some pain up front is paid back later in programmer efficiency, so long as you are careful to build reusable components. I compared against wicket, echo, echo2, jsf, tapestry, struts, laszlo, and others. --sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
