This sounds like a bug. HttpSessionBindingListener will hear the events
when an object is added and/or remove from the session object, or when the
session is invalidated, in which case the objects are first removed from the
session, whether the session is invalidated manually or automatically
(timeout).
I just tested how WebSphere 1.0 (0.91 spec) reacts, and the equivalent
<BEAN>, scope=session, does not do this.
BTW, in a previous email I stated the session object is invalidated at
browser shutdown. Of course that isn't true. The server doesn't know you
closed your browser. The session will simply timeout after a time.
Dan
> ----------
> From: Alexander Yavorskiy[SMTP:[EMAIL PROTECTED]]
> Reply To: Alexander Yavorskiy
> Sent: Thursday, April 15, 1999 12:49 PM
> To: [EMAIL PROTECTED]
> Subject: valueBound/valueUnbound
>
> When java bean implements HttpSessionBindingListener interface it gets
> notified when it is added and/or remove from the session object. That
> works
> fine if you add/remove objects to/from session manually. However, if
> USEBEAN
> tag is used with the LIFE-SPAN=session it seems to bound and unbound on
> every page request (in spite of "session" lifespan). Is this a bug in
> JRun,
> the servlet engine we are using, or it is supposed to work like that?
>
> Has anyone seen similar behavior?
>
> Thanks,
> Alex
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff JSP-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
