Hi Alex,
I would say Tapestry 5 wins the challenge unless you plane to use T4.
Tapestry 5 uses annotations, and this is a very important advanced feature
in Java. You don't need to extend WOComponent, WebPage or what ever.
I think all frameworks will use the annotations in the future; the question
is when is available.
T5 does and it's ready.
In other words, the real question you should ask "Do I want to use
annotations or classical framework?"
Try T5 a little, and you will fast mention the power of annotations.
Signature IT-Consult Armainak Sarkis
----- Original Message -----
From: "Alex Shneyderman" <[EMAIL PROTECTED]>
To: <users@tapestry.apache.org>; <[EMAIL PROTECTED]>
Sent: Wednesday, August 22, 2007 10:13 AM
Subject: wicket vs tapestry ?
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]
