Before settling on Tapestry, I tried comparing Tapestry and Wicket and I didn't like in Wicket that for each form control one has to create an instance of a class and bind it to html page. IMO this violates the DRY(do not repeat yourself) principle. This could be OK if Wicket was backed by some visual tool like .NET, but doing it manually is cumbersome. Also doing something like Tiles required creating panel classes and frankly I couldn't figure out how exactly it works. Even Wicket developers admit that Wicket may have performance issues.
Alex > I've seen the comparison of Tapestry vs JSF, but it seems one comparing to > Wicket is in order. Can anyone briefly summarise the approach and pros/cons > when comparing them? > > John > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
