Francois Beausoleil wrote:
>Hello Andrea,
>
>This has already been implemented. See Session.disconnect() in the
>documentation.
>
>Hope that helps !
>
>Bye,
>Francois
>
>
>
My application is a J2EE application, with both swing and html
interfaces (the
latter is more limited, for the public, the former is for internal
personnel with
write access...)
I load data from stateless session beans, open a session, perform database
operation, close it. I also use container manager transactions, so I
don't think
I can keep the session object around in disconnected state... what do
you think?
Best regards
Andrea Aime
|
