Life time of session bean

Question

I read in Ed Roman's book
Life time of session bean is rough equivalent to life time of session or "life time of client code that is calling the session."
"clients session duration could be as long as browser window is open" page 81
How does the server know lifetime of client code.

Answer 1

Greetings,
I read in Ed Roman's book
Life time of session bean is rough equivalent to life
time of session or "life time of client code that is
calling the session."The real point is that a Session Bean's life is relatively short since it is closely linked to the life of the client - as compared to the relatively long life of an Entity Bean which is closely linked to that of the resource's data. As an Entity Bean's identity comes from the primary key of the data to which it maps, a Session Bean's identity comes from the session id for the client which created it. When the client's session is "terminated", so is the Session Bean. The semantics of session termination, however, is dependent upon several factors...
"clients session duration could be as long as browser
window is open" page 81This is a little misleading. The browser (window) itself does not establish a connection to a Session Bean (or any EJB for that matter). However, an Applet embedded in the page which the browser is displaying might, as well as might a Servlet to which the browser is "connected". In either case, how long the Session Bean remains "alive" depends on the life of the component connecting to it. For an Applet it would generally be until the Applet's destroy() method is called. For a Servlet it would be until the client's HttpSession object is invalidated (assuming the bean reference is stored there; otherwise it's when the current service thread terminates ':-o ).
How does the server know lifetime of client code.By virtue of the fact that a connection to a Session (or Entity) Bean is synchronous - meaning there's an underlying socket connection between the client's reference (a "stub") and the bean proxy. If the client code terminates the connection terminates with it...
I hope this helps.
Regards,
Tony "Vee Schade" Cook