Bug 14004 - Incorrent behaviour of all attribute-related lifecycle event tests
Summary: Incorrent behaviour of all attribute-related lifecycle event tests
Status: NEW
Alias: None
Product: Watchdog
Classification: Unclassified
Component: Client (show other bugs)
Version: 4 (Servlet 2.3 / JSP 1.2)
Hardware: All All
: P3 major (vote)
Target Milestone: ---
Assignee: Ryan Lubke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-28 05:11 UTC by a.v.goldberg
Modified: 2004-11-16 19:05 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description a.v.goldberg 2002-10-28 05:11:09 UTC
Almost all of lifecycle event tests are based on the following assumption: all 
the listeners must finish processing events before servlet can continue its own 
execution. All these tests have the same model: listeners and servlets exchange 
information through static arraylist which is filled up by listener and then 
processed by servlet. I couldn't find any requirement in Sun servlet spec 2.3 
on the synchronization between listener and the entity which initiated the 
process of adding/removing attribute from anywhere. There are requirement 
on .valueBound()/.valueUnbound() methods and on startup/shutdown events but 
nothing on attributeAdded/Removed/Replaced() etc.
This is my undestanding and this could be wrong so I would really appreciate it 
if you could keep me posted on this.