Hi Vinod,
You seem to have taken all these things in the other way round.
Actaully except HttpSessionBindingListener and HttpSessionActivationListener, every other listeners are usually implimented by any other(non attribute) classes not the attribute class.
Please give stress on the
word usually.
Means it's not imperative.
See HttpSessionBindingListener and HttpSessionActivationListener, these two listeners have to do all the stuff with the attributes, as events trigger these Listeners only when something happens with attributes. So there is no significance in making a non-attribute class to extend these interfaces.
But for other listeners, you can have any class (attribute or non-attribute) implementing them because they are not attribute specific. But you have to provide proper implementation for all the methods defined in these interfaces.
Regards,
Khushhal