The current draft 2.3 says: "If a null value is passed, the effect is the same as calling removeAttribute()." AFAIK this was not specified in the previous versions of the spec 2.2 and earlier. (The API doc 2.2 explicitly disallow null values: "the object to be bound; cannot be null") So to be shure what happens, you should use removeAttribute() instead of passing a null value. (Unless all servlet engines you want to deploy to, implement the 2.3 spec) > -----Urspr�ngliche Nachricht----- > Von: Thomas Krebs [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 30. Mai 2001 17:59 > An: [EMAIL PROTECTED] > Betreff: setAttribute behaviour when passing null as attribute <snip/> > What is the expected result of calling setAttribute on an instance of > ServletRequest, if the attribute to be passed is null (i.e. > request.setAttribute(someName, null))? <snip/>
