Wicket's EL in templates is very limited... What Wicket's EL? Isn't there a wicket-velocity project if one wants code in templates? Or he means propertyExpressions? Anyway, wicket is better WITH theese "cons" - imho. And I can think of other non-listed cons for frameworks like tapestry or jsp (is that a "framework" really?). Framework comparisons may be good for one thing only - publicity. I, for example, first heard of wicket while reading one (heated) comparison debate on one forum.
-- View this message in context: http://www.nabble.com/Wicket%2C-Matt-Raible%27s-OSCON-presentation-tf4178586.html#a11928114 Sent from the Wicket - Dev mailing list archive at Nabble.com.
