On Thu, Jun 12, 2008 at 5:36 PM, Leffingwell, Jonathan R CTR FRCSE,
JAX 7.2.2 <[EMAIL PROTECTED]> wrote:
> It's not the "why is formName null?" that I'm worried about. In this
> case, it's supposed to be null.
>
> What I want to know is this: Is a NullPointerException supposed to be
> thrown if the argument "name" in session.getAttribute(name) is NULL? If
> such an exception IS supposed to be thrown, was this a change put into
> Tomcat 5.5.x that wasn't in 5.0.x?
I assume that it was the Hashtable -> Hashmap -> ConcurrentHashMap change.
Unlike the Hashtable and the ConcurrentHashMap the Hashmap allows
get(null) calls.
So in tomcat 50.19 - 5.0.30 & >5.5.9 is was hashmap and worked,
changed that to hashtable (5.5.16?) and stoped working, changed to
concurrenthasmap in 6.x and remained not working. My versioning might
be inaccurate, but the timeline should be approx. right
regards
Leon
P.S. probably it would be good if StandartSession would check for it
return name==null ? null : (attributes.get(name));
instead of
return (attributes.get(name));
but they probably won't do it anyway:-)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
