First let me say there seems to be quite a rivalry between the users of the frameworks. We've even had wicket fan boys join the Tapestry list with the sole intent of trolling.
One difference I know is that Wicket stores a lot more information in the session than Tapestry does. At it's core, Tapestry is much different. Please search past postings on the mailing list for some details. There are also some posts on Howard Lewis Ship's blog that specify some of the differences. On 8/22/07, Alex Shneyderman <[EMAIL PROTECTED]> wrote: > I just started to look for a component based framework. I came across > both tapestry and wicket (and it would be hard not to as you guys > share the same host) but I kind of fail to see what the differences > are? > > From my limited experiments with both, wicket and tapestry seem to be > quite similar. So, I wonder if there is anything I am not seeing? > Anyone has a comparisson map of wicket vs tapestry? > > Alex. > > PS: I like both frameworks for their lightness I just feel that I will > need to stick with one to be pragmatic :-( > > --------------------------------------------------------------------- > 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]
