How to remove a SFSB in web page??

Question

Hi all,
I have a question on when should I call remove() when ejb is involved in web pages.
I have searched the past threads in this forum and someone suggested to use http
binding interface. It is really a great idea. However, I still have two questions.
Q1. when a web session time-outs, it will trigger the http binding event. However,
how do web server know the session is time-out?
a) There is a timer in web server for each session. When a client (browser) make
a request to web server, web server will check if it is time-out or not., i.e.
the time-out is triggered from Client
b) There is a timer in web server and it will periodically check if there are
any time-out session. If yes, invalidate them.
If the answer is b, it perfects. If the answer is a, I have a concerns. If user
suddenly closes the browser, then time-out event will not trigger forever?
Q2) I am using iplanet for web server and WLS 5.1 which implies the app and web
server resides in different JVM. Is the http binding event can still be triggered
from iplanet to WLS ejb?
They make me plainful.
Frank

Answer 1

Comments embedded below
"Frank" <[email protected]> wrote in message
news:[email protected]...
>
Hi all,
I have a question on when should I call remove() when ejb is involved inweb pages.
I have searched the past threads in this forum and someone suggested touse http
binding interface. It is really a great idea. However, I still have twoquestions.
>
Q1. when a web session time-outs, it will trigger the http binding event.However,
how do web server know the session is time-out?
a) There is a timer in web server for each session. When a client(browser) make
a request to web server, web server will check if it is time-out or not.,i.e.
the time-out is triggered from Client
b) There is a timer in web server and it will periodically check if thereare
any time-out session. If yes, invalidate them.
If the answer is b, it perfects. If the answer is a, I have a concerns. Ifuser
suddenly closes the browser, then time-out event will not trigger forever?The session will be timed out if it exceeds it's max timeout value as per
the servlet spec.so you don't have to worry about A)
Q2) I am using iplanet for web server and WLS 5.1 which implies the appand web
server resides in different JVM. Is the http binding event can still betriggered
from iplanet to WLS ejb?This may in fact be a problem with your using HttpSessionBindingListener in
your case. One thing you could do instead is implement an
HttpSessionListener in your WebApp and store a Map of EJB remote references
in the session. Whenever a session is invalidated, timed out, or destroyed
for any reason the container will make a callback to the sessionDestroyed()
method of your HttpSessionListener class. In this method you could simply
iterate through the Map of references you have stored in the session that is
being destroyed and call remove() on each of those references. One thing to
keep in mind though is that both these listener classes were defined in the
Servlet 2.3 specification so if you aren't at least using that then neither
one will be available to you.
>
They make me plainful.What makes you plainful?
Frank
~Peace
rupton