Forums Register Login
AttributeListeners VS BindingListeners
I am having some problems understanding the difference in functionality provided by the HttpSessionAttributeListener interface and the HttpSessionBindingListener interface. Does anyone have an easy way of differentiating the roles of the above named interfaces?
Actually, I think I finally figured it out. Correct me if I am wrong. If I have an object aBook of type Book, then HttpSessionAttributeListener will send out a notification when an object has been added, replaced or removed from the session whereas HttpSessionBindingListener will send out a notification (as long as Book implements the HttpSessionBindingListener interface) when aBook has been bound or unbound from the session. Is this a correct?
Ricardo, this is a great question.
The only comment I can add is when you alter a session-level object (add/modify/remove) and the object implements HttpSessionBindingListener, the container calls the valueBound method and then notifies the appropriate HttpSessionAttributeListener(s).
I've also tried writing some sample code to fully understand the distinction, but so far, it hasn't caused the proverbial light to come on.
So, in other words, if I want to monitor the adding/removing/replacing of objects to the session I use HttpSessionAttributeListener and I want to monitor changes to a specific object's values then I have that object implement HttpSessionBindingListener?
I guess I never realized how good the search function of this messageboard really was...I did some searching and found several posts on the subject, including this one:

This thread has been viewed 725 times.

All times above are in ranch (not your local) time.
The current ranch time is
Oct 21, 2018 00:03:31.