Databinder 1.1 will use sessionFactory.getCurrentSession() within all
models. The default behavior will be a ManagedSessionContext bound
inside DataRequestCycle, but you can turn that off if you want to use
JTA or Spring-managed transactions:

http://www.springframework.org/docs/api/org/springframework/orm/hibernate3/LocalSessionFactoryBean.html

Nathan

Mats Norén wrote:
> Congrats! :)
> Btw, how difficult would it be to reuse the different models from
> within a Spring based solution?
> The project I'm working on uses Spring for different kinds of services
> (JBPM, Email etc) and there is a need to keep things in the same place
> so to speak but I really like the different Hibernate models you've
> created....
> 
> /Mats
> 
> On 11/22/06, Nathan Hamblen <[EMAIL PROTECTED]> wrote:
>> It's solid, as far as we can tell. :)
>>
>> There's some new documentation on the site that I hope is helpful to
>> Wicket beginners, regardless of their plans for persisting data. It's an
>> overview of IModel, why it's important, and how it helps with persistence:
>> http://databinder.net/manual/
>>
>> Nathan


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to