but those cached entities are the key :) because hib has to guarantee
instance identity within the session scope - that cache is what makes the
long-session pattern possible :)
-igor
On 2/15/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/15/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> why is it dangerous? i hope that if you disconnect the session it doesnt
> hold a ref to sessionfactory anymore. session itself is pretty light -
just
> a cache of loaded entities, it is the session factory that is a pretty
heavy
> object you dont want replicated
It's those cached entities that make it dangerous. If you have a clear
view what's in it at all times, it's fine, but with Hibernate it's
easy to let things slip past.
Eelco
-------------------------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
