On Sat, Sep 20, 2008 at 9:38 AM, <[EMAIL PROTECTED]> wrote: > I don't think there need to be a 1000 examples - a single, complete, > convincing example would be sufficient...one that can be used as a starting > point for a website (authentication, a good database layer...some ajax > samples).
Agreed. That would be nice to see a fully-functional example out there. My point was that even if there isn't one, it doesn't take long to create the stuff on your own with Wicket because it's just that easy. > My first impression of wicket (after looking at the phonebook application) > is, that lots of code examples for Ajax exist and that it looks quite good. > However there seem to be lots of configuration files, so whenever you make a > new object you need new hibernate mapping files, and several class files and > interfaces - so lots of writing. I also happenned to see a .vm file - and I > think velocity is really out-of-date....and I dont know why this is needed. 1. What configuration files are you talking about? The only configuration file required by Wicket is the web.xml file (to set up the wicket filter/servlet). That's the same as T5. Until the servlet specification comes up with a way to auto-discover web configuration objects (like the Wicket filter), we're all stuck with that one. 2. Using hibernate in Wicket is the same as any other project out there. The Wicket folks didn't write Hibernate. If you're going to use Hibernate, you have to tell it certain things to get it to work correctly. 3. Velocity isn't required at all for Wicket. However, they do have support for it in an optional library. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
