I have to agree with Igor here. I didn't have to do anything
special when I started using Wicket. The DAOs and Service tier
that I had in place worked fine.
It could be argued that if you're integrating Hibernate at the Wicket
level, something is wrong in your design. However, I understand
that for simple apps, multiple tiers is overkill. Things like
Spring's OpenSessionInViewFilter still work, or you can roll your own
filter and have it set the session in the WebSession.
Perhaps I'm confused on what you mean by integration.
- Re: [Wicket-user] Re: Standard for database integration? ... Nick Heudecker
- [Wicket-user] Re: Standard for database integration?... Nathan Hamblen
- Re: [Wicket-user] Re: Standard for database inte... Phil Kulak
- [Wicket-user] Re: Standard for database inte... Nathan Hamblen
- Re: [Wicket-user] Re: Standard for datab... Martijn Dashorst
- [Wicket-user] Re: Standard for data... Nathan Hamblen
- Re: [Wicket-user] Re: Standard ... Martijn Dashorst
- Re: [Wicket-user] Re: Standard ... Gili
- [Wicket-user] Re: Standard ... Johan Compagner
- Re: [Wicket-user] Re: Stand... Martijn Dashorst
- RE: [Wicket-user] Re: Standard for database inte... Igor Vaynberg