I didn't say my cons were valid - but I do believe there *are* cons to Wicket. What are they - in your opinion?
matt igor.vaynberg wrote: > >> * HTML templates live next to Java code > this is easily changed - just a default > >> * Need to have a good grasp of OO > why is this a con? you are saying not knowing oo is a good thing? you > can say this is a pro - learning wicket will make you a better > developer :) > >> * The Wicket Way - everything done in Java > as opposed to embedding logic in views which has been something > plaguing other frameworks for ages? > > -igor > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Matt-Raible%27s-ApacheCon-presentation-tf4815955.html#a13780519 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
