Thanks to all, I will analyse how complex my UI will be and than evaluate if Wicket fits in.
Thanks for pointing at Stripes... I always thought: "Spring is so cool, everybody says that." So SpringMVC is the way to go, but as mentioned here it is quite low-level. My today's two favourites :=) 1. Wicket - SpringCore - Hibernate 2. Stripes - SpringCore - Hibernate Thanks for pointing at http://databinder.net/site/show/overview Databinder . I will discuss with myself if abandon Spring is an option. I guess using Spring only makes sense when you have to code quite a bit of business logic. Discussion, especially arguments against Wicket, my case in mind, are welcome :=) Paul -- View this message in context: http://www.nabble.com/Is-Wicket-a-proper-framework-for-a-Webshop---tf4341788.html#a12384390 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
