On Jan 25, 2006, at 20:21, Alexander Varakin wrote:
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.
Tapestry 3 also has some replications (.page file vs. backing Java
code, if you have that), but Tapestry 4 + JDK 1.5 annotations cleans
that up nicely. The only thing I really miss would be .page file
inheritance, as others have discussed.
My largest concern w/ Wicket is its immaturity. I wouldn't want to
hang a big commercial project on it.
...Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
