The difference is that Http-SessionAttributeListener is configured in the deployment descriptor and the
container creates only one instance of the specified class. HttpSessionBindingEvents generated from all the sessions are sent to this object. On the other hand,
HttpSessionBindingListener is not configured in the deployment descriptor
This is from Hanumant deshmukh . But i have read in HFSJ that it is not reqired for Http-SessionAttributeListener to be declared in DD.
Can anyone give the explanation .