igor.vaynberg wrote: > > why dont you use the code in spring or databinder as an example then? > best way to learn anyways. >
Ha ha, that's what I was wondering. The code to integrate with an ORM either has to be in a library or in your own project. Those are the only options, and the second option kind of sucks (unless you only ever work on one Wicket project, or you like maintaing and upgrading disjoint copies of the same code). That is probably why there aren't any published and up-to-date examples of that kind of app; it's just not a compelling approach that is going to motivate someone to build and maintain example applications (generally a frustrating and thankless chore). Those that insist on taking the hard road of app-specific integration (or building their own libraries) will have to live with it being the hard road. The fact that I've put some code out there should make it easier, but the independent route will never have a chauffeur. And hey, if anyone ever has weight loss ideas for Databinder, I'm all ears (but I'd like to see your scale first). It's already broken down into modules; the only thing I could guess is that the module boundaries didn't line up exactly with a desired subset, but we can always make MOAR modules. Nathan -- View this message in context: http://www.nabble.com/Wicket-%2B-Hibernate-without-Spring-and-Databinder-tp18827595p18835350.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]
