The question is what you need more: 1. RichClient like application on the web - then you can go with vaadin, since it has many build in components 2. If you look for good perfomnace in faver of rich components then tapestry is better choice IMHO
I used vaadin for administrative application, the performance was not so important. Together with Google Guice as IoC it was nice combination. Tapestry has build in own IoC, but integrating Spring is very easy too. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry5-vs-Vaadin-tp5715273p5715274.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
