Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

listeners

 
ankit kumar
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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 .


 
Christophe Verré
Sheriff
Posts: 14691
16
Eclipse IDE Ubuntu VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The answer is in this FAQ.
 
Swathi Kota
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
HttpSessionActivationListener and HttpSessionBinding Listener need not be configured in DD. All other listeners have to be configred in DD. where was it mentioned in HFSJ that Attribute Listener need not be configured?
Thumb rule:
When the Sessionlistener purpose is to notify the attribute objects ( i.e to notify a dog object when it is added to session / migrated to another VM ) those listeners need not be declared in DD.

Please correct me if I am wrong.
 
Kamal Tripathi
Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
ankit kumar wrote:
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 .



where was it mentioned in HFSJ that Attribute Listener need not be configured?


Well HFSJ does mention that Http-SessionAttributeListener needs to be declared in the DD. However that is an errata. FAQ mentions it and you can consult the list of confirmed HFSJ errata

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic