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
-igor
On 2/15/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> And thanks Wicket guys for looking in to this; I know that what we're
> doing is a little "out there," but as Chuck said there are some pretty
> compelling uses for it, mostly in the class of ajax operations you want
> to perform tentatively, and commit later. Down the line I don't think
> this approach will be at all unusual.
It sounds interesting, but also dangerous. Keep us informed about the
pattern :)
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
