I agree that Wicket, although it's really 'only' a view framework, could do with a couple of straightforward examples in this area, because:
- A view framework without any persistence going on isn't typically very useful; - It's important, if only to learn where, how and with what to hook into various server/session/request/... lifecycle stages correctly; - Wicket should be as easy as possible to get into, and this is rather a major point, I should think; - Spring, while very useful, is just a wee bit beside the point sometimes, and you're better off using it _after_ you understand what's going on anyway. (Besides, how else could you tell if it would useful to begin with?) Cheers, Erik On Thu, Jul 23, 2009 at 11:23 PM, Dane Laverty<danelave...@gmail.com> wrote: > There we go, that's the kind of information I was looking for! Thanks John. > What got me started with Spring initially was its JDBC templates, but then > everything I read basically said, "Yeah, Spring has JDBC templates, but you > won't really need them since you should be using ORM instead." However, when > I went to find some Hibernate/Wicket examples, all the ones I found were > based in a Spring DI framework. So here I am. I'm sure it will be worth it > in the end, but at the moment it's a lot of reading and testing without > feeling like I'm being especially awesome. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
