Having gone trough a web framework evaluation myself in the last year, my recommendation is to actually build a small wicket application. The benefits over other web frameworks are very real, but not evident from studying the brochures.
Thomas > -----Original Message----- > From: René Samselnig [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 6. Februar 2008 14:13 > To: users@wicket.apache.org > Subject: Evaluating Wicket > > > Hi people, > > currently I'm evaluating wicket as the future framework in > our company. I already found a lot of information but still > there is some missing. I hope you can help me out answering > these questions. > > * What experience do you have regarding performance of wicket > applications? > * Is there a way to cluster wicket applications? > * Does wicket use any proprietary, non-standard technologies? > * How does wicket care about session hijacking or sql injection? > * Is there an easy way to implement SSO? > * Can I integrate wicket applications into any content > management system? > > If you have an answer to any of these questions don't > hesitate to ignore the others - any input is welcome! > > Thanks in advance, > René > -- > View this message in context: > http://www.nabble.com/Evaluating-Wicket-tp15306535p15306535.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
