billbarker    01/10/03 19:20:04

  Modified:    src/facade22/org/apache/tomcat/facade HttpSessionFacade.java
  Log:
  Remove validity checks from where the spec doesn't require them.
  
  This fixes Bug #3920 submitted by Alessandro Polverini [EMAIL PROTECTED]
  
  Revision  Changes    Path
  1.17      +0 -3      
jakarta-tomcat/src/facade22/org/apache/tomcat/facade/HttpSessionFacade.java
  
  Index: HttpSessionFacade.java
  ===================================================================
  RCS file: 
/home/cvs/jakarta-tomcat/src/facade22/org/apache/tomcat/facade/HttpSessionFacade.java,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- HttpSessionFacade.java    2001/09/23 00:24:52     1.16
  +++ HttpSessionFacade.java    2001/10/04 02:20:04     1.17
  @@ -113,7 +113,6 @@
       // -------------------- public facade --------------------
   
       public String getId() {
  -     checkValid();
        return realSession.getId().toString();
       }
   
  @@ -140,7 +139,6 @@
       }
       
       public long getLastAccessedTime() {
  -     checkValid();
        return realSession.getTimeStamp().getLastAccessedTime();
       }
   
  @@ -295,7 +293,6 @@
       }
   
       public int getMaxInactiveInterval() {
  -     checkValid();
        // We use long because it's better to do /1000 here than
        // every time the internal code does expire
        return (int)realSession.getTimeStamp().getMaxInactiveInterval()/1000;
  
  
  


Reply via email to