tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session
Date Tue, 22 Mar 2005 14:58:22 GMT

----- Original Message ----- 
From: "Remy Maucherat" <>
To: "Tomcat Developers List" <>
Sent: Tuesday, March 22, 2005 1:57 AM
Subject: Re: cvs commit: 

> wrote:
>> billbarker    2005/03/21 19:50:03
>>   Modified:    catalina/src/share/org/apache/catalina/session
>>   Log:
>>   From the comments for R1.11, it seems that some early version of the 
>> spec had an exception here.  However, this didn't survive to the final 
>> spec version, so we can once again allow access to getLastAccessedTime 
>> from an invalid session.
>>   Fix for Bug #34107
>I didn't know that, as the javadoc actually says:
>public long getLastAccessedTime()
>     Returns the last time the client sent a request associated with this 
> session, as the number of milliseconds since midnight January 1, 1970 GMT, 
> and marked by the time the container received the request.
>     Actions that your application takes, such as getting or setting a 
> value associated with the session, do not affect the access time.
>     Returns:
>         a long representing the last time the client sent a request 
> associated with this session, expressed in milliseconds since 1/1/1970 GMT
>     Throws:
> >>>        java.lang.IllegalStateException - if this method is called
>on an invalidated session
>Which paragraph in the spec has the conflicting statement ?

It's the java-doc for jakarta-servletapi-5 that is wrong.  The javadocs in 
the servlet spec do not contain a 'throws' clause.  See also:


To unsubscribe, e-mail:
For additional commands, e-mail:

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

View raw message